We're seeing a good number of DEAD_LINE EXCEEDED errors again (with HTTP 500 status codes) and have yet to come up with a good way to handle them. Here's the problem:
- I try to create a new event in gCal and get an HTTP 500 response with the body: "com.google.calendar.server.CalendarException: com.google.net.rpc.RpcException: /MessageRouterUploadService.Upload to 10.91.100.4:9225 [DEADLINE_EXCEEDED]" - in many (all?) cases the event is in fact created in gCal, but I don't know what its <id /> is so I can't reference it in the future - since I can't uniquely identify the event I just created, I'm left trying to guess which event in my calendar it is, which gets ugly fast What I'd like to see is the insert operation either succeed and return the GData representation of the event including the <id /> (like it usually does) or fail and not insert the event into the calendar. Right now it's successfully doing the insert but failing to return the GData for the event. This problem has been discussed previously on this group, but we don't seem to have come very far on it. (See <http://groups.google.com/group/ google-calendar-help-dataapi/search?group=google-calendar-help- dataapi&q=deadline_exceeded>.) Any suggestions or additional information? Thanks, Charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
