Frank_Dawson@xxxxxxxxx wrote:
>So, to summarize, the sequence number is always the same for all
>instances, and it must always be the highest sequence number. Right?Effectively, I think so. That is, you received an initial REQUEST (implicitly with SEQUENCE:0), a subsequent ADD (with SEQUENCE:1) and then a reschedule of an instance (with SEQUENCE:2).
So, if an Attendee asked for a REFRESH, then the subsequent REQUEST would specify at least SEQUENCE:1. I say at least SEQUENCE:1 because we have allowed in iTIP that each message sent by the Organizer can involve an increment to the SEQUENCE property. I know of one implementation that seems to do this.
-- Frank
begin:vcard n:Mansour;Steve tel;fax:650-937-2103 tel;work:650-937-2378 x-mozilla-html:FALSE org:Netscape version:2.1 email;internet:sman@xxxxxxxxxxxx title:Judge, Jury, and Executioner adr;quoted-printable:;;501 East Middlefield Road=0D=0AMS: MV-054;Mountain View;CA;94043; x-mozilla-cpt:;-10552 fn:Steve Mansour end:vcard