[dev] [cvs] commit: kronolith/lib/Driver kolab.php

[Chuck Hagenbuch]

Quoting Gunnar Wrobel <wrobel at pardus.de>:

>> So how do you handle the case where two people have the same
>> invitation on their calendars?
>
> I'm not certain what could be a possible error scenario here. Within
> Kolab the ID is local to each calendar and does not care much about
> the ID in other calendars. And I guess having the same UID across
> calendars is meant to be used that way or am I wrong?
>
> I admit that I'm not that certain why Horde actually uses two types of
> ID. Somehow I was unable to give both a very clear and precise
> meaning. Maybe you could clarify the exact meaning or give me a hint
> where to look it up as this is a central part for handling all the
> external data exchange correctly and I definitely want to get that
> part right.

In the SQL driver, all events are in one database table. When someone  
syncs with a device using SyncML, or receives an iCal invitation, we  
need to maintain the UID of the original event so that we can track  
updates to it later.

Therefore the UID can't be the event_id, because if two people on the  
same Kronolith install received the same invitation, the uid for both  
events (as added to their personal calendars) will be the same.

-chuck