Re: RFC libksync

Am Wednesday 29 May 2002 15:41 schrieb Cornelius Schumacher:
> On Thursday 23 May 2002 00:13, Holger Freyther wrote:
> > Am Wednesday 22 May 2002 23:36 schrieb Cornelius Schumacher:
> > > > it should include all necessary metainformations( id
> > > > replacement )
> > >
> > > You can't replace ids. If an entry has an id, syncing musn't alter
> > > it. Otherwise things like group scheduling get broken.
> >
> > In cases of Opie uids you may alter it. Group scheduling isn't a
> > problem. Could you explain it a bit more.
>
> In vCalendar and iCalendar the unique id is required to be globally
> unique and musn't be changed after an event has been created. This
> allows to identify events even across systems and after sending via
> email.
>
> For group scheduling the id is used to associate events with reponses to
> scheduling messages. E.g. if you send a proposal for a meeting to some
> people and you get back a counterporposal or a confirmation, it's
> possible to associate the response with the original request.
>
> I believe that no syncing code should rely on being able to change the
> id or to store extra information in the synced entries in any other
> way, because this will break if there are restrictions on the synccees
> side that don't allow that.
Ok,
My current syncing hack works the following way.
In this example when talking about devices i mean libkcal on a desktop and 
Opie on a remote device.
Opie got integer uids (-12345678) where uniqueness is not really available. 
Now when syncing I look if anything in a category( todo) is associated with 
-12345678 if yes I'll take KDEs ids which would be libkcal-232434546dfdg. If 
it's not associated I prepend a Konnektor- to it.
When now the Data with the uid gets synced (libkitchensync) it looks for the 
"Konnektor-" and if found assigns a uid (CalendarFormat::generateUID() ) to 
it. The it adds the association to the list.
On a second sync you've the associations. For Opie this is a favorable 
solution cause it lacks Group-Scheduling. For KDE it's favorable too. A 
integer uid is not guranteed to be unique.
But this is  my point of view. The uid is not getting lost and seamless 
Group-Schedulung will not be disabled.

regards Holger


_______________________________________________
kde-pim mailing list
kde-pim@xxxxxxxxxxxx
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/