-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30 May 2006, at 15:26, Chris Withers wrote:
Jens Vagelpohl wrote:
Persistent caches can introduce odd errors, unfortunately. They
can create inconsistencies between what a ZEO client thinks the
database state is and what the ZEO server thinks. Not recommended
for production setups.
Don't necessarily agree with this. If the clients get in a tiz,
that's a bug that should be fixed.
There are several production setusp where I use persistent client
caches and I've had very few problems with them...
I'm sorry, this is not a matter of "agreeing". It is a matter of
personally observed facts.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEfFaNRAx5nvEhZLIRAhl/AKCsPm4lQeHr4JAAgWwOsRZGaMBt7QCfUo0E
1bx2oQocV666c3XajSnQBh0=
=et2a
-----END PGP SIGNATURE-----
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
