[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Recurrence ID changes?




Bruce is correct, I was wrong. Sorry. The response to the REFRESH would be a single REQUEST. Responses to a REFRESH are always a REQUEST reflecting the current state of the calendar component description.

However, all iTIP methods are not full snapshots. For example, the CANCEL and REPLY are are examples of shortened messages. The CANCEL need not have a copy of all of the properties of the calendar component that is being cancelled. Like wise with the REPLY. FYI.

Thanks, Bruce.

>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).