Doug climed on 05/23/2003 02:01:28 PM: > Not true. > > RECURRENCE-ID is only like UID when the SEQUENCE and UID are known. > So RECURRENCE-ID applies to the verison of the object where UID > and SEQUENCE match the update.
Sorry but _that_ is not true.
Go recheck RFC 2446, Section 2.1.5 Message Sequencing:
To maximize interoperability and to handle messages that arrive in an unexpected order, use the following rules:
1. The primary key for referencing a particular iCalendar component is the "UID" property value. To reference an instance of a recurring component, the primary key is composed of the "UID" and the "RECURRENCE-ID" properties.
2. The secondary key for referencing a component is the "SEQUENCE" property value. For components where the "UID" is the same, the component with the highest numeric value for the "SEQUENCE" property obsoletes all other revisions of the component with lower values.
So RECURRENCE-ID is used in conjunction with UID and BEFORE SEQUENCE checking. Why? Simple: you have to find the right instance before you can check if the message is older, newer, etc.!
Which was my point!? You will notice that UID *was* in my sentence you quoted!? As was SEQUENCE.
> A RECURRENCE-ID by itself has no meaning. Only when the SEQUENCE > number and UID are known does RECURRENCE-ID have any meaning.
Nope, go reread that bit and check the ordering again...
I do not need to, you correctly quoted the RFC above. It is only usable when UID and SEQENCE are known.
Doug Royer | http://INET-Consulting.com -------------------------------|----------------------------- Doug@xxxxxxxxx | Office: (208)612-INET http://Royer.com/People/Doug | Fax: (866)594-8574 | Cell: (208)520-4044
Description: S/MIME Cryptographic Signature