I have modified ZSyncer to be able to "pull" objects backwards. This was relatively straightforward. I would be happy to send you some code ... what would be best for you? The new Product or diffs on the old one? Additionally, since you seem in a mood to develop ZSyncer, maybe you and the Zope list could comment: I'd like to use ZSyncer to sync code that is external to ZODB, e.g. External Methods and Python Products. At this point, I'm just hacking away to get it in there, mostly using os.system and such. But I would be happy to rethink and refactor if the community think it's worth the effort. I think in the long run, Zope needs this functionality. Thoughts? Ziniti Andreas Hölzl wrote:

hi to all the ZSyncer user out there,

ZSyncer is quite a fine Product, but i'm missing bidirectional syncing, i.e. being able to do an update of remote objects as well as local ones from one ZSyncer instance. The current state is, if i am right, only one way syncing. Example: if there is an object on your remote Zope and it is missing on your local Zope, you can only delete the object on the remote server but not copy it to your local Zope. I suppose this has to do with the 1-to-n (development-production) syncing architecture.

If no one can explain or has a suggestion, i'll try to modify ZSyncer by my self.

Andreas Hölzl

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )