Hi,
Shouldn't it be hidden in pypi? Or is it useful?
http://pypi.python.org/pypi/ZODB4
regards,
Christophe
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
On Oct 20, 2008, at 9:28 AM, Christophe Combelles wrote:
Hi,
Shouldn't it be hidden in pypi?
I think it should be removed. No one should be using it.
Or is it useful?
No.
http://pypi.python.org/pypi/ZODB4
I'm not an owner of that. I wonder who on this list is.
Someday, there will be
On Mon, 2008-10-20 at 11:12 -0400, Jim Fulton wrote:
I'm not an owner of that. I wonder who on this list is.
I guess it's nobody, except if Jeremy is still reading. (Jeremy? Are you
out there?)
I guess we could ask a PyPI admin to give us ownership.
Someday, there will be a ZODB 4. It will
If an object is modified on one ZEO client, will this always lead to a
__setstate__ call on this object on another ZEO client?
If not, is there any event or method that I can hook into to determine
if an object was modifed by another ZEO client?
--
Roché Compaan
Upfront Systems
I would not imagine this functionality is not in scope of the ZODB. We
were thinking about piggy backing on top of the invalidation messages
sent from ZEO server at one point.. cant remember why we gave up on
it.
For various reasons:
- The object may not be loaded on the other zeo client;
