View of /PEAK/TODO.txt

Parent Directory

Revision Log

Got rid of deprecated 'peak.model' classes: Model, Package, Reference, etc.

Open Issues/To-Do Items


 Targeted for 0.5 Alpha 1

    * Fix issue w/reading XMI 1.1 files where metamodel has nested packages

    * Refactor "Pythonic" UML 1.3 extensions so they're usable for most
      MOF-aligned metamodels (e.g. all UML and CWM versions)

    * Get XMI writing in place, w/transaction support

    * Document interface expected of "active descriptors" and their complements
      (e.g. __class_provides__), refactoring for cleanliness as needed.

    * Updated reference docstrings for 'peak.api', 'peak.binding',
      'peak.config', 'peak.exceptions', and 'peak.naming'.

    * Finish tutorial chapter 2 (?)


 Targeted for 0.5 Alpha 2

    * On-the-fly class combination (think "runtime module inheritance",
      without the modules) for DMs.

    * ZConfig support, probably in the form of generating ZConfig schemas
      from 'peak.model' or MOF models, but maybe in the form of 'fromZConfig'
      constructor methods as well.

    * 'peak.running' refactorings: use standard 'logging' module's log levels,
       add 'logging' distro to 'peak.util' for 2.2 backward compatibility,
       make daemons based on 'peak.model' (or at least define ZConfig schemas),
       and possibly adjust cluster stuff to work off ZConfig primary and
       generate clustertools file(s).  App startup tools based on ZConfig and
       PEAK-style .ini files.

    * 'peak.naming' refactorings: 'peak.model'-based syntax utilities for
       creating address syntaxes.


 Targeted for 0.5 Final Release (or sooner)

    General

        * Tutorial complete through chapter 4

    peak.storage

        - unit tests for more complex object scenarios: references, thunks..?

        - lock management interfaces/API

        - docstrings for reference

    peak.model

        - 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

        - 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.

        - simple daemons comparable to those in MetaDaemon, unit tests

        - 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

        - 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

    * Implement WarpCORE-oriented structural model, w/Querying support

    * "Indexed" version of in-memory model?


    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

    * 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)