[Subversion] / PEAK / TODO.txt  

Diff of /PEAK/TODO.txt

Parent Directory | Revision Log

version 663, Sun Nov 10 21:13:42 2002 UTC version 689, Sun Nov 17 01:27:14 2002 UTC
Line 3 
Line 3 
   
  Targeted for 0.5 Alpha 1   Targeted for 0.5 Alpha 1
   
       * Finish tutorial chapter 2
   
     * Updated reference docstrings for 'peak.api', 'peak.binding',      * Updated reference docstrings for 'peak.api', 'peak.binding',
       'peak.config', 'peak.exceptions', and 'peak.naming'.        'peak.config', 'peak.exceptions', and 'peak.naming'.
   
     * Additional content for the tutorial's chapter on binding  
   
   
   
  Targeted for 0.5 Final Release (or sooner)   Targeted for 0.5 Final Release (or sooner)
Line 15 
Line 15 
   
     General      General
   
         * Update tutorial documentation          * Tutorial complete through chapter 4
   
         * Up-to-date and complete Persistence package  
   
   
     peak.storage      peak.storage
Line 32 
Line 30 
   
         - unit tests for more complex object scenarios: references, thunks..?          - unit tests for more complex object scenarios: references, thunks..?
   
         - SQL field type conversion for txnTime?          - SQL field type conversion for txnTime? Should already happen
             for Sybase and Postgres which select the time. So, what to do
             about ManagedConnection's txnTime?
   
         - lock management interfaces/API          - lock management interfaces/API
   
Line 45 
Line 45 
   
         - clean up TW docstrings & interfaces          - clean up TW docstrings & interfaces
   
       peak.naming
   
           - useful example "flat" naming context (e.g. like AppUtils.URLkeys)
   
           - useful example hierarchical naming context (e.g. like JNDI's LDAP
             context or filesystem context)
   
           - rework smtp: to return a factory object that supports open().
             Also think about whether smtp should move elsewhere. Maybe
             there should be peak.network or peak.internet for things like
             smtp, ftp, etc contexts?
   
     peak.running      peak.running
   
Line 54 
Line 65 
           the clusterit tools to choke or barf on the file, or which would            the clusterit tools to choke or barf on the file, or which would
           produce ambiguous or unintended results.            produce ambiguous or unintended results.
   
         - create a basic LogFile logging provider w/URL comparable to AppUtils          - finish misc tasks on peak.running.logs's TODO list
   
         - simple daemons comparable to those in MetaDaemon          - simple daemons comparable to those in MetaDaemon
   
Line 62 
Line 73 
   
         - docstrings for reference          - docstrings for reference
   
   
     peak.config      peak.config
   
         - "Rule"-oriented configuration files (section specifies component          - "Rule"-oriented configuration files (section specifies component
           rather than property name prefix).            rather than property name prefix), so that daemons and other simple
             apps can be fully configured and run via a config file.
   
   
     peak.util      peak.util
Line 80 
Line 91 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
  Future Releases   Future Releases
   
   (Note: some of the below is held-over from TransWarp and may no longer be    (Note: some of the below is held-over from TransWarp and may no longer be


Generate output suitable for use with a patch program
Legend:
Removed from v.663  
changed lines
  Added in v.689

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help