Re: request + add

"Mark Smith" <[email protected]> wrote in message
news:[email protected]...
>
> Michael Fair wrote:
> >
> > "Mark Smith" <[email protected]> wrote in message
> > news:[email protected]...
> > >
> > > 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.
> >
> > I'm not quite sure how to respond to this.
> > I assure you that I responded accurately and completely to a
request+add.
>
> Re check what you send, there is NOT a ADD.
>
> > > >   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
> > > >
> >
> > How is this not the example given?
>
> The example given was ADD which is NOT the object above.
> See the original post and section "3.2.4 ADD" in iTIP.

I think you are misunderstanding what object it is that's being
described here.

Here's what happened:
Organizer sends an ADD
A2 having determined that it missed something requests a REFRESH
Organizer sends a REQUEST in response to the REFRESH

The object above that you keep saying is not an ADD, but imply
should be an ADD, is the response object from the ORGANIZER to
A2's REFRESH request.

It is not an ADD (just as you said) and should not be an ADD
(as you are implying).

The above object is a recurring event that has per instance data
which needs to be communicated.  The above object is the proper
object with which describe the complete state of UID:XXX at SEQ:2.

What else could it be?

-- Michael --