[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Recurrence ID changes?
Dan replied:
>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.
I agree w/this but that is not how Frank described it in his response to you. He 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.
This is incorrect, no?? The actual format of the multipart/related would be the full snapshot of the current REQUEST (not the "initial" REQUEST) and then the exception modification in a separate body part.
I think we are all in agreement here; I just wanted to make sure there was no confusion about the contents of the multipart related (ie: the original REQUEST and then a delta or set of some deltas up to the current SEQUENCE, etc).
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...