How can Attendee know that Organizer does not exist in system anymore
Please pardon my ignorance. I have a question of CalDav Protocol * I have an organizer, 'User1' * I have an attendee, 'User2' * User1 organized an event with User2 * Now User1 got removed from the system. Maybe he did not do any actions on the event he created. His account got removed. How can User2 know that User1 no longer exist and the event in his calendar is invalid??? Regards, Gaurav Jain
User 2 (Attendee) keeps doing Accept/Decline but status of the event does not change. On Tue, Feb 17, 2015 at 11:57 AM, Gaurav Jain <monkeyfdude@gmail.com> wrote:
Please pardon my ignorance. I have a question of CalDav Protocol
* I have an organizer, 'User1' * I have an attendee, 'User2' * User1 organized an event with User2
* Now User1 got removed from the system. Maybe he did not do any actions on the event he created. His account got removed.
How can User2 know that User1 no longer exist and the event in his calendar is invalid???
Regards, Gaurav Jain
Hi Gaurav, --On February 17, 2015 at 11:58:55 AM -0800 Gaurav Jain <monkeyfdude@gmail.com> wrote:
User 2 (Attendee) keeps doing Accept/Decline but status of the event does not change.
The server is supposed to add a "SCHEDULE-STATUS" parameter on the ORGANIZER property whenever it attempts to send a scheduling message reply to the organizer. Fort a successful reply the code will be a 1.x or 2.x code. For a failure, it will be a 5.x code. Clients can use that value to determine whether scheduling is working or not. See <http://tools.ietf.org/html/rfc6638#section-7.3> for more details. -- Cyrus Daboo
Thanks a lot. Yes it is 5.3...Thank you very much!!!! On Tue, Feb 17, 2015 at 12:10 PM, Cyrus Daboo <cdaboo@apple.com> wrote:
Hi Gaurav,
--On February 17, 2015 at 11:58:55 AM -0800 Gaurav Jain < monkeyfdude@gmail.com> wrote:
User 2 (Attendee) keeps doing Accept/Decline but status of the event does
not change.
The server is supposed to add a "SCHEDULE-STATUS" parameter on the ORGANIZER property whenever it attempts to send a scheduling message reply to the organizer. Fort a successful reply the code will be a 1.x or 2.x code. For a failure, it will be a 5.x code. Clients can use that value to determine whether scheduling is working or not. See < http://tools.ietf.org/html/rfc6638#section-7.3> for more details.
-- Cyrus Daboo
participants (2)
-
Cyrus Daboo
-
Gaurav Jain