[Zope] More ZSyncer stuff

[Andy]

> Hi Andy,
>
> I hope you dont mind the emails.. I'm basically sending you my brainstream
> about your timesaving product

No thats fine, glad its being used.

> Two suggestions:
> 1) Have a 'ignore' status for each item, with a grey box. That way certain
> items will never be compared in the XMLRPC stream and are safe.

Yeah, I was thinking of hardcoding in some ignore values, but also allowing
arbitrary objects to be ignored. The big problem here is *folders*. If you
sync the containing folder, it will happily sync all the subobjects,
ignoring these objects you told it to ignore. What we need to be able to do
is separate and somehow sync each object individually, thats really tricky
to do, folders are a problem.

> 2) Is it possible to check that an object is a product and a product that
> would not allow transfer, such as SQLSession object.

I dont know how I could check that... if make the ignore list an option for
the user, once they find and object that cant be synced, they can add it to
the list for their ZSyncer.

> 3) An Authorization request is thrown when trying sync apparently
> non-syncable objects (my SQLSession objects). I tried using a
> manageinterface added user and it had no difference than superuser in
> inituser. The Authentication is an impossible one because it doesnt accept
> the correct password and then after 3 tries you get the gratuitous page

If a product behaves funnily theres not a lot I can do. Error could be nice
though. See point 2.

> 4) Sometimes in root, a folder will be green, but you know there are
> contents that are not. Go into that folder and you have some items that
are
> yellow.

Yes folders again. If you change an object in folder, the object becomes out
of date. However since you have not changed the folder, it is still green.
Now if you rename, add, delete, copy, cut into / out of that folder (ie
change the number of objects) the folder has changed. Hence the folder is
now out of date.

Folders are a problem.

> 5) Sometimes in a folder, EVERYTHING is yellow (out of date) when you know
> only one is. This is SCARING the shit out of me because i work on a site
> that has a folder which does credit transactions... Not knowing what is
> going on there is dangerous. If you update the object anyways, what
happens
> I wonder?

Well dont use it then, please dont screw up your site with it. We sync what
we know to need changing, figuring what has changed is still fraught with
problems.

The problem is we are comparing date / times on objects and sometimes they
just appear to be plain wrong. Especially if you are syncing to a box in a
different time zone! What is needed is something me and Gregor are talking
about, a version number on each object, similar to CVS. By comparing the
number of a version, we eliminate this problem.

--
  Andy McKay