[ZODB-Dev] ZEO features

[Elliot Lee]

On Fri, 13 Jul 2001, Jeremy Hylton wrote:

> I'm saying that ZEO is the wrong place to introduce remote
> method invocation.  ZEO doesn't know anything about objects.  It just
> serves pickles to a ZODB process that knows how to handle them.

If only I had my brain on straight... I was just thinking about ZEO from
the newbie's point of view, where it has "something to do" with remote
objects.

So it sounds like that instead of my view, which was:
	remoteobj.value -> ZODB -> ZEO -> network -> ZEO -> ZODB -> localstorage
reality is more like:
	remoteobj.value -> ZODB -> ZEOStorage -> network -> localstorage
And ZEO just proxies the storage API...?

[Assuming this is correct.]

Since it appears that it is possible for more than one ZODB.DB to be
attached to the same storage object, would it be possible to have
the remote client and my in-process app server using the same data store,
leaving things more like so:

	remoteobj.value -> ZODB -> ZEOStorage -> network -> ZEOServer -> myserver.localstorage
	myserver.localobj.value -> ZODB -> myserver.localstorage
	remoteobj.method() -> bastardizedZEOStorageConnection -> network -> bastardizedZEOserver -> myserver.localobj.method()

-- Elliot
Your freedom to change my source code does not translate into my
responsibility to foist your changes upon users at large.