Hi.
I am trying to have a ZODB.DB accessible from remote locations trough
ZEO.ClientStorage . I want the remote clients to also be able to work
disconnected (by enabling ClientStorage's local caching).
The problem is that changes made in one place do not show up in any other
places (trough
Hi All,
This is with whatever ZODB ships with Zope 2.8.5...
I have a Stepper (zopectl run on steroids) job that deals with lots of
big objects.
After processing each one, Stepper does a transaction.get().commit(). I
thought this was enough to keep the object cache at a sane size, however
[Chris Withers]
This is with whatever ZODB ships with Zope 2.8.5...
Do:
import ZODB
print ZODB.__version__
to find out.
I have a Stepper (zopectl run on steroids) job that deals with lots of
big objects.
Can you quantify this?
After processing each one, Stepper does a
Mihai Ilinca wrote at 2006-1-26 15:10 +0200:
...
Trough 'slave' I only do read operations at the moment. If I make changes to
the stored data trough the 'main' client, the 'slave' clients don't see it.
They only see the data as it was when the ClientStorage was constructed. If I
restart a
[Mihai Ilinca]
...
In addition to what Dieter said (thanks, Dieter!),
...
Trough 'slave' I only do read operations at the moment.
You didn't say which version of ZODB you're using. If it's a version before
3.3, then a client that doesn't modify objects may not process invalidations
even
I have some code that might be worth putting into ZODB.
There are three bits.
- Two flavors of persistent queue. Both have a conflict resolution
policy to be about as lenient as I could make it. They don't expect
to ever hold multiple instances of equivalent values at the same
time.
