[Zope-PTK] Separating code, design, and content -- a stop-gap solution?

[Spicklemire, Jerry]

Bjorn said:

> Allright, this has been talked about before, and several
> not-very-good-but-posssible solutions have been mentioned.

<snip some ideas relating to the "separation" beast>

> Of course, later, I hope the content could be in a different Storage
> (Mountable Storage), allowing for a smooth upgrade by atomically
> switching from one ZEO client to another, both running with the same
> content Storage.  Is that possible?

It seems possible to me, as witnessed by a precipitous leap 
to the exact same conclusion, upon the announcement of the 
"Mountable" File Storage, Databases, etc.

http://www.zope.org/Members/tseaver/Projects/HighlyAvailableZope/DevTestProd

However, "now how do you find stuff" once the benefits of 
acquisition are removed, due to total logical, and physical 
seperation. Here we are, back to explicit references to 
everything, and suddenly mixing it all together doesn't 
look that bad . . .

The only thing I've been able to come up with (conceptually) 
is to define storages by object type, and to layer yet another 
"meta-Zope" Storage that knows about all possible storages. 
Then you could binds types, and therefore sources, to object 
names but at the cost of losing the ability to override with 
a local object of the same name. Whew!

There is some fundamental Zen that applies here, no doubt, 
but this "Grasshopper" has far to go along that path . . .

Later,
Jerry S.