[ZODB-Dev] Re: StandaloneAdaptableStorage

[Jeff Kowalczyk]

My interest is with a package name that reflects that there will be
a lot of plug-ins for various parts of AdaptableStorage someday,
and the namespace of specialized storages, mappers and other parts,
as well as composite combinations will in time be fortunately
crowded.

It seems that AdaptableStorage will be offering the kinds of code-
executes-when hooks that Aspect Oriented Programming does, with a
general focus on persistence and included support for persisting by
ZODB.

AdaptableStorage seems hard to name because the package is (I
think) aspect machinery. I don't know what I'd call the internals
of the AspectJ compiler, either.

If that assessment sits well, it seems that we could find a
comfortable coexistence with aspect terminology by expecting that
machinery implementing AS to have its own naming peculiarities, but
that the specializations, strategies, and mappings that developers
create with it could then be named in aspect-fashion.

Perhaps this anticipation of a great many small and large
specializations will suggest a name more related to the resulting
customizations than about the core and first-tier add on
implementation components.

So, what about some brainstorming in the word family:

Persistence Aspects Library

pal
PAL
palib
pasplib
perasplib
paf       (framework)
PAF

Perhaps Standalone AdaptableStorage decomposes to a series of
smaller extensible libraries:
(aspectlib, persistlib, mapperlib, storagelib, zodblib, zopelib)
grouped underneath a catchier top-level name.