[ZODB-Dev] transaction issue

[Erik A. Dahl]

OK, this works but now I'm confused. I thought that if an object was
updated then commited from one ZEO client that it would be invalidated
in the cache of all other ZEO clients (which clearly isn't happening). 
My app has an external status checking program that updates an object if
its status is bad (which should be very infrequent).  The problem of
course is that if there is an update I need to know about it soon.  Is
there a way I can mark an object as invalid from the writer client
without having to flush the entire cache of all of my reader clients
(which it looks like sync() does)?

-EAD 

On Thu, 2002-04-11 at 10:12, Greg Ward wrote: 
> On 11 April 2002, Erik A. Dahl said:
> > I'm totally new to the zope/zodb/zeo thing so this may be a stupid
> > question... I'm accessing zope objects in a zeo database from an
> > external zeo client.  When I make changes through the zmi I don't see
> > them in my external client until a disconnect and reconnect.
> 
> Call the sync() method on your Connection object.
> 
>         Greg
> 
> 
> _______________________________________________
> For more information about ZODB, see the ZODB Wiki:
> http://www.zope.org/Wikis/ZODB/
> 
> ZODB-Dev mailing list  -  ZODB-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zodb-dev