[ZODB-Dev] StandaloneAdaptableStorage

[Shane Hathaway]

Adrian van den Dries wrote:
> On March  3, Shane Hathaway wrote:
> 
>>I think "tom" might be the right name, then.  The "zFoo" convention has 
>>been used up, and lowercase seems to be preferred among Pythonistas.
> 
> 
> adaptablestorage or AdaptableZODBStorage.  Keystrokes are cheap.
> 
> Or XStorage. (Whee! X!)
> 
> tom conveys zero information about what it is, or does.

AdaptableStorage conveys the wrong message.  Most of the package does 
not depend on ZODB, and you can do more with it than just "store" 
things.  AdaptableStorage is a temporary name designed to discover the 
level of interest in this functionality.  It has been received well, but 
from what I can tell, people are equally interested in the rest of the 
functionality, but it's currently concealed by the name of the product.

Toolkit for Object Mapping conveys the right message.  Suggestions are 
welcome, as long as they don't involve "Zope", "ZODB", "Storage", "DB", 
"Connection", or "Relation".

> Is there any chance of it being rolled into ZODB proper?

Only some of it.

> Frankly, I don't understand the "standalone" releases: Zope should
> depend on ZODB, and ZEO should depend on ZODB and the Storages are
> plugins for ZODB, which may or may not supply a ZMI interface to them.
> Then the release procedure should just package up the appropriate bits
> with scripts, instead of the CVS symlink mess.  (I still haven't
> figured out how I can maintain a production Zope/ZEO setup from CVS,
> not that I've tried particularly hard.)

Do you need some help with something?  The symlinks aren't beautiful, 
but they are centrally managed, you can ignore them for the most part, 
and they work *much* better than what we were doing before.  Here is 
where they are managed:

http://cvs.zope.org/CVSROOT/repolinks?rev=HEAD&content-type=text/vnd.viewcvs-markup

Shane