Agreable, but regarding one point that if things are a bit funny, dont use it. It's either useable or not in this context, so is there anything you can add as far as the risks involved? Let me state a scenario: A subfolder you have entered in ZSync has almost ALL items as out of date but you know only one or two are ACTUALLY out of date. What could happen if you sync the in-date, out of date items? From the way I see it, it only refreshes the copy of the object to be (theoretically) the same as it was before the update... (follow me?) Is it possible that this misnomered sync could cause garbage to go in, or clear the contents of the object or....
From what you say that only the datetime is compared, than if the site you are working on is fully functional, then a misnomered sync in fact doesnt do anything, except for update the datetime to what it understands as 'proper'
Have I confused you sufficiently? ; ) Paz -----Original Message----- From: Andy McKay [mailto:andym@ActiveState.com] Sent: 08 June 2001 17:47 To: Paul Zwarts Cc: Zope Subject: Re: [Zope] More ZSyncer stuff
Is this somehow related to the mxDateTime thread and something about Zope returning DateTime objects as strings? Perhaps using mxDateTime is a good idea then? Personally, I've lost alot of time wrestling with DateTimes that sometimes go into a sql table and sometimes not. I had assumed it was just my newbieness (and still do) but something tells me I'm not as stupid as I think I am :-)
I think just comparing date times is just inherently problematic, there has to be a better way for this particular application. The ZSyncer aint CVS, yet :) Cheers. -- Andy McKay.