But a Full refresh response would be all the events with their Recurrence-ids
If I get an INSTANCE modification to an instance that does not exist, then I'll do a REFRESH.
What do you do when you get a modification to an instance that does not exist in your calendar?
Blindly accept it and accept there is never any way to get the original and never know what to do with future updates that may change that same RECURRENCE-ID you do not have?
Wait for an object that may never arrive with a lower
sequence number?Do a REFRESH just for that instance that you do not have because it is in the SEQUENCE:0 object you do not have?
Do a REFRESH with the same RECURRENCE-ID you just got? Which is a modification to an object you do not have.
What do you do with the second instance modification to a UID you do not have? Loop forever?
You use REFRESH by ATTENDEEs of 'existing' events, not new invitations:
The "REFRESH" method in a "VEVENT" calendar component is used by "Attendees" of an existing event to request an updated description from the event "Organizer". The "REFRESH" method must specify the "UID" property of the event to update. A recurrence instance of an event may be requested by specifying the "RECURRENCE-ID" property corresponding to the associated event. The "Organizer" responds with the latest description and version of the event.
Doug Royer | http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@xxxxxxxxx | Office: (208)612-INET
http://Royer.com/People/Doug | Fax: (866)594-8574
| Cell: (208)520-4044Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature