[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RECURRENCE-ID discussion
Doug didnt get it on 08/07/2003 04:10:54 PM:
> > > In Bruces model you can NEVER add someone to the series
> > > of recurring VEVENT after any change that effects the
> > > effective DTSTART value
> > Huh?? You are really not getting the fixed model I think.
> > RECURRENCE-IDs used never change then adding someone is no big
> > Take a look...
> > If for some reason I wanted to add you to an instance of:
> > UID: 1
> > SEQUENCE: 10
> > RECURRENCE-ID: 20030805T180000Z
> > DTSTART: 20030816T150000Z
> > then I send you just that. Your REPLY would use the same
> > RECURRENCE-ID / SEQUENCE value that someone who is aready invited
> > and we would all be on the same page. Where is it broken??
> That example of mine was NOT to a single instance - what's your point?
The point I was making is that its 100%
easy and straight forward adding ANY ATTENDEE at ANY time after SEQUENCE:0
in "my" (aka iCalendars) model. I just moved SEQUENCE ahead
to 10 to reuse the fragments already in play but I see that easily confused
some folks. Sorry about that.
Lets see if I can rephrase the point
for you: Adding new ATTENDEEs at ANY TIME is no problem with a fixed RECURRENCE-ID
model; your claim of "you can NEVER add someone
to the series...after any change"
is just flat out wrong. Yep, that about rephrases it just right.
Above was an example of how easy it
is to add someone to a single instance, I simply send them a REQUEST using
the current definition and thats it. Adding them to the set is just
as easy. I showed how easy it was last month when Arnaud asked for
examples. To save time and effort Ill let you go check the archives
for 'em if you are still unsure how it can be done.
Messaging & Collaboration
IBM Software Group
FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...