--------------------------------------------------------------------
TODO    TODOTODOTODOTODOTODOTODOTODOTODOTODOTODOTODOTODOTODO    TODO


If anyone is interested in contributing to the feature set, please
subscribe to the perl-objectstore mailing list.  Send email to
majordomo@parallax.co.uk with the following in the body of the
message:  "subscribe perl-objectstore you@your.company.com"


Optimize for flexibility, then memory performance, then speed.

1. Flexibility
Flexibility is the most important because ObjectStore should be
easier to use and everyone complains that it can't do SQL.
We'll show 'em!

2. Memory Performance
Memory performance is also very important due to the potential size of
databases.  Small memory efficiency improvements in a 5TB database
have a big impact.

3. Speed
Speed is pretty good already, compared to a relational database.
Of course, there is always room for improvement!


+ IDEAS +

Better test scripts for sets?

Avoid stomping on some other version of ref,bless?  Nah.

Strings can be turned into BLOBs and back.  BLOBs support various
indexing, including Verity TOM.  Verity full text indexing.

Programmer friendly C++ / Java access to persistent perl data structures

Support for notification.

Support for database access control?

Support for the database utility API?  Who cares?

Does anyone want ObjectStore pvars?

Track down any/all XS transient memory leaks.  (Any?)


+ CORE-PERL WISH LIST +

There should be a less kludgy way to extend bless and ref.  Why aren't
these special methods of UNIVERSAL?  :-(

Why do FIRSTKEY, NEXTKEY accept a string instead of a (string, length) pair
or an (SV*)?  The TIE interfaces should be more XS friendly!

Make 'reftype' an official built-in!

+ BIGGISH PROJECTS +

Split out representations into their own shared libraries.  Requires
support for multiple application schemas.

Mesh with Java.

Arrays.  Maybe wait until perl-porters fix the TIEARRAY interface.
Add support for parts of the TimeSeries Object Manager?

Could perl performance be improve?  Streamline typemap?  Cache TIED
method entry points?

[HARD] Add MOP support for editing & reporting of abritrary databases.
Object Design working on this problem?

Expand Maker to encompass all architectures/compilers/situations.
Integrate with and replace MakeMaker?  Why bother?

