Dieter Maurer wrote:
Chris Withers wrote at 2006-5-1 11:34 +0100:
...
...well, there are .zec files in the var directory, so I guess I must
be. What controls whether a persistent or temporary client cache is used?
Your Zope configuration file, of course ;-)
Yeah, I knew that bit of it ;-)
Tim Peters wrote:
it knew about. To support this, a persistent ZEO cache stores the
value of the largest tid the ZEO client knew about in the cache file.
Hmmm, didn't think I was using a persistent client cache here...
...well, there are .zec files in the var directory, so I guess I must
Chris Withers wrote at 2006-5-1 11:34 +0100:
...
...well, there are .zec files in the var directory, so I guess I must
be. What controls whether a persistent or temporary client cache is used?
Your Zope configuration file, of course ;-)
It is the client option of the zeoclient section.
You
[Tim]
No, I don't. The internal docs/comments are inconsistent on this
point. FileCache.settid() starts with
##
# Update our idea of the most recent tid.
[Chris]
Is this the most recently used or the most recently available?
(possible off-by-one error)
Neither, really. It's the
Not sure if Jeremy still on this list so CCing...
Tim Peters wrote:
No, I don't. The internal docs/comments are inconsistent on this
point. FileCache.settid() starts with
##
# Update our idea of the most recent tid.
Is this the most recently used or the most recently available?
Hi Tim
Just been digging some more on this issue and found:
http://mail.zope.org/pipermail/zodb-checkins/2004-January/008063.html
In every case I get this error, the tid's are equal, which suggests your
notes about the = potentially being bad were correct ;-)
I'm low on fu here, so what's
Hi All,
Anyone else seen this?
(864) CW: error in notifyConnected (('x', y))
Traceback (most recent call last):
File C:\Zope\2.9.2\lib\python\ZEO\zrpc\client.py, line 506, in
notify_client
self.client.notifyConnected(self.conn)
File C:\Zope\2.9.2\lib\python\ZEO\ClientStorage.py, line
