Re: request + add

Michael Fair wrote:

> >
> > Okay, now what if it gets the sequence:1 request and the sequence:2 'add'
> > as shown in 'B'.  As all three instances can not be represented in
> > one 'method request' object because the duration of all three instances
> > are not the same. Now the master object is at sequence:2, as is
> > attendee-2.
> 
> This can actually be described in one method:request object as I'll
> demonstrate below in response to a REFRESH request.  You are right
> if what you meant was that it can't be described in 1 VEVENT component.

However you did not do a request+add below which was the question.
You did a request + single instance reschedule.

> > The recurrence-id's can be calculated from what attendee-2 has. Correct?
> > And it will be the same recurrence-id's as organizer. Correct?
> 
> This sounds correct, but since we haven't rescheduled any of the instances
> yet it's not all that meaningful... 

As this topic is part of EXPAND:TRUE debate - yes it is valid.

Your example below is not the one asked.

> 
> The ORGANIZER will send the following message in response to the REFRESH:
> BEGIN:VCALENDAR
>   METHOD:REQUEST
> 
>   BEGIN:VEVENT
>    UID:XXX
>    SEQUENCE:2
>    ...
>    DTSTART: 1-dec-2003 at noon
>    DTEND: 1-dec-2003 at 1pm
>    ...
>    RDATE:3-dec-2003 at noon
>    RDATE:2-dec-2003 at 3:30
>   END:VEVENT
> 
>   BEGIN:VEVENT
>    UID:XXX
>    RECURRENCE-ID:2-dec-2003 at 3:30
>    SEQUENCE:2
>    ...
>    DTSTART: 2-dec-2003 at 3:30
>    DTEND: 2-dec-2003 at 5pm
>    ...
>   END:VEVENT
> 
> END:VCALENDAR
>