-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Paul Winkler Sent: Wednesday, November 20, 2002 9:52 AM To: zope@zope.org Subject: Re: [Zope] Zsyncer to Zuploader
On Wed, Nov 20, 2002 at 12:39:44PM +0100, Elena Schulz wrote:
Hi,
does anybody know what needs to be done to change the Zsyncer-Product so that it just serves as an uploader without needing to be installed on the client-side (if possible). Or is there an other solution to upload Zope-Objects with properties (without zexp-import)
when you say "client", do you mean the source? For starters, ZSyncer uses a push model, not a pull model. You push from the source to the destination. And it uses xml-rpc to call zsyncer methods on the destination. I don't know diddly about xml-rpc in zope, aside from what zsyncer does. You'd have to replace those calls, if possible, with suitable rpc calls to things in the zope API, and if that won't do the job, you'll need to create some methods on the remote server. ZSyncer takes the latter approach by providing everything you need to be a source or a destination in one product.
I think what you want is too different from the way zsyncer is designed, you might do better to start from scratch, maybe stealing ideas from zsyncer source.
I think (and I'm taking a wild stab here) that what Elena wants to do is use zsyncer with freezope. freezope won't install zsyncer for security reasons, since a zsyncer can pretty much install anything it wants. If this is the case, a better approach might be to create a restricted zsyncer that only creates objects from a pre-specified list of types. This is not just a bit of hackery as it is a philosophical shift for zsyncer: away from an admin-only mirroring tool and toward a user development tool. You would have to make other changes as well (such as removing the logfile pathname from the UI). No, I'm not volunteering, though it sounds like a worthy project.