[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Recurrence ID changes?
If all
changes could be rolled into a single instance, then I agree. For
instance, if only the date-time changed then addition of an EXDATE and RDATE
properties to the original component would suffice.
However, as soon as you change anything else about an individual
occurrence (i.e. Subject, Attendees, Categories,etc) then this cannot be
represented in a single component. One component must be sent for the
original event definition and another component would have to be sent with the
individual RECURRENCE-ID changes.
Dan
Frank wrote:
>The response to the
REFRESH for the whole recurrence set
>could be the initial REQUEST, followed by the
reschedule
>REQUEST, in a
multipart/related container. Right?
Actually I dont think so. Why would you send 2
entries, the "original" and the "update"?? Aren't
all messages supposed to be 'full snapshots'? If so, only the 'current
' state needs to be sent. Hence, if the SEQUENCE was 'stale' then the
Organizer would send a new full snapshot in a single message; not a 'base'
and then the most recent 'delta' (as that wont suffice at all).
Bruce
===========================================================================
Bruce
Kahn
INet: Bruce_Kahn@iris.com
Iris
Associates
Phone: 978.392.5335
Westford, MA, USA 01886
FAX:
and nothing but the FAX...
Standard disclaimers apply, even where
prohibited by law...