[Tickets #8956] Re: Reschedule of recurrent events duplicate entries on attendee calendars

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8956
------------------------------------------------------------------------------
  Ticket             | 8956
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Reschedule of recurrent events duplicate entries on
                     | attendee calendars
  Queue              | Kronolith
  Version            | Git master
  Type               | Enhancement
  State              | Accepted
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2010-07-08 19:14) wrote:

Since we now store relationships between exceptions and their related  
recurring event, it seems to me we can do the following:

If it's being rescheduled to a different date/time, we can send an  
iTip with just this modification, with the UID and RECURRENCE-ID  
fields filled in appropriately.

If the event instance is outright canceled, send an iTip representing  
the entire event series, with appropriate values for EXDATE. Yes, this  
would also have to include the vEvent components for any already  
existing rescheduled exceptions, but that seems to me to be ok since  
all the vEvent components would be for the same UID. (As I understand  
RFC 2446, you can have multiple vEvent entries in the single iCalendar  
REQUEST if they all reference the same UID).

Sound right, or am I missing something?