Thank you so much. Let me try. I will update this thread. On Thu, Oct 12, 2017 at 12:44 PM, Cyrus Daboo <cda...@apple.com> wrote:
> Hi Gaurav, > > --On October 12, 2017 at 12:19:53 PM -0700 Gaurav Jain < > monkeyfd...@gmail.com> wrote: > > How would the scheduling operation would look for this use case? >> >> I read RFC 6638 but it only explains: >> >> B.7. Example: "Attendee" Declining an Instance of a >> Recurring Event >> ............................................72 >> <https://tools.ietf.org/html/rfc6638#page-72> >> B.8. Example: "Attendee" Removing an Instance of a >> Recurring Event >> ............................................75 >> <https://tools.ietf.org/html/rfc6638#page-75> >> >> >> It does not explain declining multiple instances of a recurring event. >> >> >> Can you please help? >> >> > The Attendee's client has two options: > > 1) Just add an overridden component for each instance being declined and > set the attendee's PARTSTAT to DECLINED (as per example B.7). The client > can keep incrementally adding an override and writing to the server as the > user declines one at a time. > > 2) Remove any overridden instances for the instances being declined and > add an EXDATE for each declined (removed) instance (as per example B.8). > This can also be done incrementally. > > -- > Cyrus Daboo > >
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-users
