[Kroupware] Synchronization of deleted data
Martin Konold
martin.konold at erfrakon.de
Tue Jul 1 19:07:39 CEST 2003
Am Dienstag, 1. Juli 2003 17:48 schrieb Jason A. Pattie:
Hi Jason,
> >This is not necessary!
>
> We are thinking about working on a synchronization layer for MultiSync
> (multisync.sf.net) that will do Kolab <-> MultiSync. This will allow
> synchronization of Kolab Calendar,
> Contacts, and Todos with any MultiSync aware plugin/application.
Good! I am looking forward to this effort.
> >No, it would only fill up the disk unnecessarily.
>
> We were thinking that the clients (non-kroupware aware) would need some
> way to know that the events they have that are no longer on the server
> really need to be deleted. Leaving the messages on the server in a
> deleted state (we thought) would facilitate this.
No, this is not required. Actually I wrote a detailed description how reliable
synchronisation works. Can you read German?
> >This is a wrong assumption.
> >This is not how disconnected IMAP works. There is no "reappearing"
> > messages issue.
> >
> >Please also have a look at
> >
> > http://asg.web.cmu.edu/cyrus/rfc/draft-ietf-imap-disc-01.html
>
> Looked at it. I'm a little confused by <lastseen> as a UID. Is this a
> user's ID (like a login ID) or the ID of a message for that user?
Basically what happens is that the UID is a strict ascending number and
therefor if a UID smaller than lastseen is not available on the server
anymore is must have been deleted.
So Deleted messages are all messages with UIDs smaller than the largest UID
but not present on the server anymore.
Regards,
-- martin
Dipl.-Phys. Martin Konold
e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Nobelstrasse 15, 70569 Stuttgart, Germany
fon: 0711 67400963, fax: 0711 67400959
email: martin.konold at erfrakon.de
More information about the Kroupware
mailing list