[Tickets #1107] RESOLVED: Meeting attendees get email with bogus UID for cancelled or changed event

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1107
-----------------------------------------------------------------------
 Ticket             | 1107
 Updated By         | kevin_myer at iu13.org
 Summary            | Meeting attendees get email with bogus UID for cancelled or changed event
 Queue              | Kronolith
 Version            | 2.0
 State              | Resolved
 Priority           | 1. Low
 Type               | Bug
 Owners             | Horde Developers
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-04-09 18:19) wrote:

Also, one other area for you to think about.  Similar situation but
different application.  We're going to have to come up with an offline
solution so some of our itinerant staff can view their calendars when
they're on the road.  One option is using a Palm (but syncing them is
conceptual only, at this point, since we must have serial devices
currently).  The other option is to use Apple's iCal and export your
Kronolith calendar and import it into iCal.  But, because UIDs are not
preserved when the information is exported from iCal and imported back into
Kronolith (because the import method always returns a new UID), you end up
with duplicate events.  I don't know the iCal spec in any great detail -
_should_ events generated in one system maintain their UID in another
system?  Should an export from Kronolith that's imported into Apple's iCal,
that's exported from iCal and imported into Kronolith have the same UID the
whole way through?  And if it should, and we can make the import function
become aware of existing events by matching UIDs, then I think we can have
ourselves a poor man's sync, and a palatable offline solution.