[ZODB-Dev] ZClients not updating

[sean.upton@uniontrib.com]

No, my application does not use connection.sync() - yet; forgive my
ignorance, but I'm assuming that this is done on each client?  What I'm
hoping for is invalidation messages from the ZSS to the clients; perhaps I'm
hoping for too much?

Here is my scenario: accessing a Zope property sheet for an object: someone
makes changes from a property sheet page on node1, clicks submit, and a
load-balancer/proxy-server redirects the next request after changing
properties of an object to the same property sheet on node2, but with old
cached values.  I'm looking for a way to avoid this.

Sean

-----Original Message-----
From: Christian Robottom Reis [mailto:kiko@async.com.br]
Sent: Wednesday, November 14, 2001 8:49 AM
To: sean.upton@uniontrib.com
Cc: tjenkins@devis.com; zodb-dev@zope.org
Subject: RE: [ZODB-Dev] ZClients not updating


On Wed, 14 Nov 2001 sean.upton@uniontrib.com wrote:

> I have seen this too before; I think this has to do with the client cache.
> Any thoughts on solutions for invalidating cached objects?

Even when calling connection.sync() the old objects are retrieved?

> the users make changes to the site through the private zeo client, the 2
> public zeo clients are for public viewing.  We've noticed that
> occasionally the changes made on the private zeo client are not
> propagated to the public zeo clients.  We have to restart them before
> the changes show up on the public zeo clients.

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