[Dev] Re: [Design] PIM needs SIM -- how about an IMP?

[Michael R. Bernstein]

(moving discussion to Dev list)

On Sun, 2002-11-03 at 17:47, Craig Allen wrote:
>
> If, as stated on the "technology" page, ZODB is in the lead to be the 
> persistent store, then does this open up a potential Zope front end?
> 
> Would it be safe to assume that plugging a Chandler ZODB data store (in 
> its simplest form, a single file) into a Zope configuration would allow 
> some or all of the Zope functionality and programmability to be applied 
> to it?

Unless Chandler uses a heck of a lot more of Zope's infrastructure than
just the ZODB, this is unlikely to be as straightforward as you suggest.
ZPublisher's object publishing is nowhere near as transparent as the
ZODB's object persistence is, attribute Acquisition is deep in
everything, and the Zope management interface has it's own set of
inheritance requirements.

Zope 3's redesign is intended to lessen (perhaps eliminate) the base
class inheritance tax, so as to make Module and Package re-use with Zope
simpler, but my understanding is that this would pretty much still
require developing a Chandler specific web-UI at the very least.

> I realize that it might not be feasible to use Zope and Chandler 
> at the same time against the same database.

Actually, this is the part that is easiest, as ZODB includes ZEO (Zope
Enterprise Objects), a technology for mounting a local 'ClientStorage'
(instead of a FileStorage) slaved to another ZODB Storage Server
elswhere.

http://www.amk.ca/zodb/zodb-zeo.html
http://www.zope.org/Documentation/Books/ZopeBook/current/ZEO.stx

So, provided that everything else is solved, all that would be
neccessary to have Chandler and Zope running out of the same ZODB would
be for each to be using their own ZODB with a mounted ClientStorage
pointing to the same Storage Server ZODB.

Cheers,

Michael bernstein.