Property to identify that server has processed the event
On the client, I am trying to differentiate b/w sent and unsent events. The event which has *organizer as the only attendee* has same propeties as set by the client when drafting that event. Server did not add anything that could tell me that it indeed was successfully processed by server. I was expecting a schedule-status property or event status property....but it was not there. is there a property to identify that server has processed the event? Best Regards,
On Mar 19, 2015, at 1:41 AM, Gaurav Jain <monkeyfdude@gmail.com> wrote:
Server did not add anything that could tell me that it indeed was successfully processed by server.
I was expecting a schedule-status property or event status property....but it was not there.
is there a property to identify that server has processed the event?
Hi, I don’t think so, but the http response code when you send the event should be an indication of the overall success or failure in handling that event. Also, again I don’t think an event with the organizer as the only attendee is a very good test case. Probably the only time an event should be in that state is while you’re still adding attendees, before you send the event. -dre
Yeah..you are correct...my concern is that I do not force user to add an attendee while creating an event. So, I need to handle all these cases correctly. Its an experiment to find out if VEVENT can be used for VTODO..... On Thu, Mar 19, 2015 at 11:36 AM, Andre LaBranche <dre@apple.com> wrote:
On Mar 19, 2015, at 1:41 AM, Gaurav Jain <monkeyfdude@gmail.com> wrote:
Server did not add anything that could tell me that it indeed was successfully processed by server.
I was expecting a schedule-status property or event status property....but it was not there.
is there a property to identify that server has processed the event?
Hi,
I don’t think so, but the http response code when you send the event should be an indication of the overall success or failure in handling that event. Also, again I don’t think an event with the organizer as the only attendee is a very good test case. Probably the only time an event should be in that state is while you’re still adding attendees, before you send the event.
-dre
On Mar 19, 2015, at 12:12 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:
Its an experiment to find out if VEVENT can be used for VTODO.....
Hi, I’m all for experimentation, however I’m curious why you wouldn’t want to use VTODO for task items. I can’t personally enumerate all the reasons that VTODO exists as a distinct component type, but I feel confident in saying that there are reasons :) Looks like RFC 2445 <https://www.ietf.org/rfc/rfc2445.txt> contains the formal definitions of the VTODO and VEVENT component types, in section 4.6. -dre
I intend to use VTODO. Right now I only use VEVENT. Conceptually I do not support TODO items YET. But while I use VEVENT, I do not force user to add attendee......the by-product of that is that organizer can create an event just for himself. Which effectively can be a TODO item for the Organizer. I did not intend it this way. It turned out this way. Now I am just testing various use-cases. When I conceptually support TODO, I will use VTODO as that is right way to do things. Best Regards, On Thu, Mar 19, 2015 at 3:33 PM, Andre LaBranche <dre@apple.com> wrote:
On Mar 19, 2015, at 12:12 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:
Its an experiment to find out if VEVENT can be used for VTODO.....
Hi,
I’m all for experimentation, however I’m curious why you wouldn’t want to use VTODO for task items. I can’t personally enumerate all the reasons that VTODO exists as a distinct component type, but I feel confident in saying that there are reasons :)
Looks like RFC 2445 <https://www.ietf.org/rfc/rfc2445.txt> contains the formal definitions of the VTODO and VEVENT component types, in section 4.6.
-dre
participants (2)
-
Andre LaBranche
-
Gaurav Jain