Roché Compaan schrieb:
If you have common add/edit methods in your app used by all of your
classes, you could do application level replication between Zopes. We
have written a small replication module for on of our apps that copes
extremely well with disconnected Zopes, and replicates a very
On Fri, 2006-07-14 at 08:58 +0200, Joachim Schmitz wrote:
Roché Compaan schrieb:
If you have common add/edit methods in your app used by all of your
classes, you could do application level replication between Zopes. We
have written a small replication module for on of our apps that copes
No problem, but remember this is app specific and still works with the
ZODB distributed with Zope 2.7.
I recently tweaked it to work with Zope 2.8.7 (remember my query about
self._p_jar._storage._serial a week or two ago?) .. The only change needed
was s/_serial/_tid/ :
def log(self,
Tres Seaver wrote:
Zope Corporation's Zope Replication Services products operates along
those lines:
http://www.zope.com/products/zope_replication_services.html
Yeah, but you can only write to one of the storages, right?
Chris
--
Simplistix - Content Management, Zope Python Consulting
Chris Withers wrote:
Tres Seaver wrote:
Zope Corporation's Zope Replication Services products operates along
those lines:
http://www.zope.com/products/zope_replication_services.html
Yeah, but you can only write to one of the storages, right?
Chris
The $10k price tag doesn't help either.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Spencer wrote:
Would it be possible for two ZODBs to keep in sync with one another,
through a mechanism similar to what ZEO employs? The idea is to make a
something like a ZEO client that can survive being cut-off from the
server, by having
