[Subversion] / PEAK / README.txt  

Diff of /PEAK/README.txt

Parent Directory | Revision Log

version 1130, Mon May 19 17:33:59 2003 UTC version 1496, Wed Nov 26 23:53:22 2003 UTC
Line 1 
Line 1 
 PEAK Release 0.5 alpha 2  PEAK Release 0.5 alpha 3
   
  Copyright (C) 1996-2003 by Phillip J. Eby and Tyler C. Sarna.   Copyright (C) 1996-2003 by Phillip J. Eby and Tyler C. Sarna.
  All rights reserved.  This software may be used under the same terms   All rights reserved.  This software may be used under the same terms
Line 41 
Line 41 
   
  Package Features   Package Features
   
     As of version 0.5a2, PEAK features include:      As of version 0.5a3, PEAK features include:
   
     * A component binding framework that makes it easy to parameterize      * A component binding framework that makes it easy to parameterize
       components and thus more easily combine and "wire" them together.        components and thus more easily combine and "wire" them together.
Line 116 
Line 116 
       from PEAK models (and vice versa) is possible (although        from PEAK models (and vice versa) is possible (although
       not yet implemented for anything but MOF->PEAK).        not yet implemented for anything but MOF->PEAK).
   
   
   
   
   
   
     * Application Runtime tools, including:      * Application Runtime tools, including:
   
       - a "command objects" framework for creating command-line applications,        - a "command objects" framework for creating command-line applications,
Line 143 
Line 148 
         large or complex applications consisting of components from diverse          large or complex applications consisting of components from diverse
         providers.          providers.
   
         - a "process supervisor" framework for multiprocess servers using
           long-running child processes (created via 'fork()') to take maximum
           advantage of multiprocessor machines for CPU-intensive services.
   
     * AOP and SOP: PEAK allows you to separate concerns as modules, then      * AOP and SOP: PEAK allows you to separate concerns as modules, then
       combine the modules via a "module inheritance" technique.  This        combine the modules via a "module inheritance" technique.  This
       lets you define a generated business object model as a        lets you define a generated business object model as a
Line 180 
Line 189 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
  Third-Party Software Included with PEAK   Third-Party Software Included with PEAK
   
      All third-party software included with PEAK are understood by PEAK's       All third-party software included with PEAK are understood by PEAK's
Line 192 
Line 215 
      please see the 'src/kjbuckets/COPYRIGHT.txt' file for details of its       please see the 'src/kjbuckets/COPYRIGHT.txt' file for details of its
      license.       license.
   
      The 'persistence' and 'ZConfig' packages are Copyright Zope Corporation       The 'datetime', 'persistence' and 'ZConfig' packages are Copyright Zope
      and contributors; please see the 'LICENSE.txt' files in their directories       Corporation and contributors; please see the 'LICENSE.txt' files in their
      for details of their licenses.       directories for details of their licenses.
   
      The 'fcgiapp' module is Copyright Digital Creations, LC (now Zope Corp.);       The 'fcgiapp' module is Copyright Digital Creations, LC (now Zope Corp.);
      see the 'fcgiappmodule.c' for details of its license.  In the same       see the 'fcgiappmodule.c' for details of its license.  In the same

Generate output suitable for use with a patch program
Legend:
Removed from v.1130  
changed lines
  Added in v.1496
cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help