View of /PEAK/TODO.txt
Parent Directory
| Revision Log
Revision:
600 -
(
download)
Tue Nov 5 02:19:47 2002 UTC (21 years, 4 months ago) by
pje
File size: 4783 byte(s)
* Added 'binding.Constant(key, value)', which allows you to specify
a constant value to be used as a property or utility in that
component subtree.
* Added storage.get/begin/commit/abortTransaction() APIs for ease
of use in short scripts. Defined a default provider for
ITransactionService in peak.ini that provides each component root
with its own TransactionService instance. It's easily replaceable
with other allocation strategies, if it should be needed. I may
change this later to a per-root strategy, since the current strategy
requires creating localConfigs for each component root. We'll see
what actual use has to say about the best way of doing it.
* Fixed a problem with local/global config object startup that could
cause "phantom" configuration objects to appear via recursion of
getLocal() or getGlobal().
* Got rid of binding.meta.assertInterfaces, which is no longer needed
because the Interface package now correctly handles metaclass
instances.
* Got rid of Singleton, since it's not used for anything and I could
neither think of any use cases nor remember why I added it in the
first place!
* Made it possible for CachingProviders to cache per-localConfig as well
as per-object. This is handy for implementing per-hierarchy services,
like the TransactionService provider mentioned above.
* Misc. TODO updates.
Open Issues/To-Do Items
Targeted for 0.5 Final Release
General
* Update tutorial documentation
* Up-to-date and complete Persistence package
peak.storage
- URLs and drivers for gadfly, Sybase, and postgres
- LDAP schema properties, SQL type mapping utilities
- Rack -> DM
- "facade" DM base class(es)
- "query" DM base class(es)
- unit tests for more complex object scenarios: references, thunks..?
- docstrings for reference
peak.model
- add support for lazy-loaded attributes
- review XMI/Querying extensions for forward compatibility planning
- clean up TW docstrings & interfaces
peak.running
- create a basic LogFile logging provider
- unit tests for daemons?
- simple daemons comparable to those in MetaDaemon?
- docstrings for reference
peak.binding
- object names/paths
- docstrings for reference
peak.config
- docstrings for reference
peak.naming
- docstrings for reference
peak.util
- docstrings for reference
- more unit tests?
Future Releases
(Note: some of the below is held-over from TransWarp and may no longer be
relevant as written, they are being kept on this list as placeholders for
ideas or problem areas that may need to be re-considered in future.)
Simulator/Module Inheritance
* Need a strategy for handling "del" operations; they are currently
untrapped. This might be okay under most circumstances, but need to
consider edge cases.
* 'makeClass()' should probably become part of the core API, where
it can be used to resolve __metaclass__ conflicts during the first
pass of importing a module (prior to running 'setupModule()')
Messaging/ObjectSpaces
* Support for sending and receiving remote cache invalidation
messages between RecordManagers.
peak.model
* Review other-end-notification protocols in the light of managed storage
models (e.g. database Records using virtual sequence objects as fields)
* Marshalling interface in Services; implementations for Enumeration, etc.
* More S-E-F metadata: features, subclasses, svc.<->class, nested services
* A way to generate Z3 Interfaces from Feature-based specifications?
* Implement WarpCORE-oriented structural model, w/Querying support
* "Indexed" version of in-memory model?
* "Persistent" StructuralModel (indexes w/BTrees? Catalog?)
Queries
* Refactor to use interfaces, if appropriate
* Incorporate into AbstractModel?
- Pros:
* Queries always available
* Each StructuralModel implementation can easily include its own
performance-tuned version of the basic items.
- Con: default implementation doesn't perform well on large datasets
* How much of framework needs extensibility? Should the predicate
classes be placed in the StructuralModel's namespace so that predicates
have their meaning assigned by the StructuralModel implementation?
peak.metamodels.uml
* Need to write an MMX or XMI -> Python generator, and hook it back up into
the UML package, since we're right now relying on a module generated
by code that depends on stuff which is going away.
* Helper methods in Elements & Services for marshalling, common queries, etc.
* Generator framework
- Tagged values in stereotypes vs. main values?
- Should tagged values be copied directly into templates? Treated as
Python expressions?
- Should Services be generated using an Element class' "static"
(class-scope) methods/attributes?
- Are association-ends scoped?
- Would it be better to seperate them?
- What determines whether an implemented Service actually stores objects
or delegates this to its subclass services?
* Simple Zope product demo (upload XMI, then browse the model via the web)
peak.metamodels.xmi
* Re-org to self-contain all XMI stuff inside an _XMI sub-component/service
* Refactoring to pure S-E-F model using Persistence
* Document version of standard used
* Metamodel identity/version checking
* XMI.Writing
* Strict parsing and/or diagnostics on files that don't match the metamodel?
* UUID/GUID support
* Support for advanced references, external references?
* XML Namespaces (do any current XMI tools need this? Which spec version
requires this?)
* DOM StructuralModel (so files can be edited without affecting vendor XMI
extensions)