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;
