| Open Issues/To-Do Items |
Open Issues/To-Do Items |
| |
|
| Targeted for 0.5 Final Release |
|
| |
|
| General |
Targeted for 0.5 Alpha 1 |
| |
|
| * Update tutorial documentation |
* Finish tutorial chapter 2 |
| |
|
| * Up-to-date and complete Persistence package |
* Updated reference docstrings for 'peak.api', 'peak.binding', |
| |
'peak.config', 'peak.exceptions', and 'peak.naming'. |
| |
|
| * Review possible cross-locational or "root" things like |
|
| 'PropertyName' -- should these things move to the API? |
|
| Or where? They're not 'util' things, certainly. Perhaps |
|
| there should be a 'peak.core' module or package for things |
|
| that are foundational to all the packages? |
|
| |
|
| peak.storage |
|
| |
|
| - URLs and drivers for gadfly, Sybase, and postgres |
Targeted for 0.5 Final Release (or sooner) |
| |
|
| |
|
| |
General |
| |
|
| |
* Tutorial complete through chapter 4 |
| |
|
| |
|
| - LDAP schema properties, SQL type mapping utilities |
peak.storage |
| |
|
| |
- LDAP field type conversion |
| |
|
| - Rack -> DM |
- Rack -> DM |
| |
|
| |
|
| - unit tests for more complex object scenarios: references, thunks..? |
- unit tests for more complex object scenarios: references, thunks..? |
| |
|
| - docstrings for reference |
- SQL field type conversion for txnTime? Should already happen |
| |
for Sybase and Postgres which select the time. So, what to do |
| peak.binding |
about ManagedConnection's txnTime? |
| |
|
| - object names/paths |
- lock management interfaces/API |
| |
|
| - docstrings for reference |
- docstrings for reference |
| |
|
| |
|
| peak.model |
peak.model |
| |
|
| - add support for lazy-loaded attributes |
- add support for lazy-loaded attributes |
| |
|
| - clean up TW docstrings & interfaces |
- clean up TW docstrings & interfaces |
| |
|
| peak.config |
|
| |
|
| - docstrings for reference |
|
| |
|
| peak.naming |
peak.naming |
| |
|
| - clarify requirements re: initial context, and add SPI functions |
- useful example "flat" naming context (e.g. like AppUtils.URLkeys) |
| to initctx, so that that can be the right way to get such APIs |
|
| (e.g. getURLContext()). |
|
| |
|
| - review context interfaces and URL hooks/hacks |
- useful example hierarchical naming context (e.g. like JNDI's LDAP |
| |
context or filesystem context) |
| |
|
| - docstrings for reference |
- 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 |
| |
|
| - more docs for new 'cluster' tools |
- more docs for new 'cluster' tools |
| |
|
| - create a basic LogFile logging provider |
- make 'cluster' parser complain about things that would cause |
| |
the clusterit tools to choke or barf on the file, or which would |
| |
produce ambiguous or unintended results. |
| |
|
| |
- finish misc tasks on peak.running.logs's TODO list |
| |
|
| - unit tests for daemons? |
- simple daemons comparable to those in MetaDaemon |
| |
|
| - simple daemons comparable to those in MetaDaemon? |
- unit tests for daemons |
| |
|
| - docstrings for reference |
- docstrings for reference |
| |
|
| |
peak.config |
| |
|
| |
- "Rule"-oriented configuration files (section specifies component |
| |
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 |
| |
|
| - docstrings for reference |
- docstrings for reference |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| 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 |
Diff of /PEAK/TODO.txt
Parent Directory
| 
Revision Log