[ZODB-Dev] ZEO Client cache invalidation?

[Christian Robottom Reis]

On Thu, 5 Jul 2001, Greg Ward wrote:

> The Connection class has a 'sync()' method which does exactly what you
> want.  Eg. in our web application, we do
>
>   get_connection().sync()

/me cries and cries.

> around an asyncore main loop; the client side of ZEO (ClientStorage I
> guess) registers a bit of code with asyncode to handle "certain
> communications" from the ZEO server (I'm not sure what distinguishes

So this is out of band from the conventional sync() mechanics.

> those communications) that announce "someone else just committed objects
> 3, 7, and 19 -- you'd better invalidate and/or reload them".  I'm not
> sure if ClientStorage just invalidates those objects in its cache or
> actually reloads them -- either way, it means Zope doesn't have to do an
> explicit Connection.sync() on every hit, because it's done
> behind-the-scenes between hits.

Is sync() _that_ heavy a load?

Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311