Hello, First, kudos on a really nice Ajax/HTML calendar interface. I really like it, and I routinely receive a number of positive comments about how nice it is.
I realize the gdata API is beta, but it would be helpful to know if the currently undocumented interfaces are going to be changed in incompatible ways or not. F.e. as you know the way EXDATEs are handled is by appending '_' + an RFC 2445 DateTime string to the Id of a cancelled event. This is a perfectly sensible thing to do (and I vote you keep it this way), but since it isn't documented anywhere and I had to reverse-engineer how this works I'm a little worried you may change this behaviour in the future. I can only assume it won't be long before a large (and quickly growing) number of folks who are using their ScheduleWorld accounts to sync their cell phones (etc...) will be starting to sync their Google calendar as well. Hopefully Google won't mind folks with upwards of 29,000 events/calendar :) It would be greatly appreciated if someone from Google could comment on the stability of the _beta_ API. This will help me set the expectations of existing and new users who will be syncing to/from Google calendar. Thank you. -- Free replacement for Exchange and Outlook (Contacts and Calendar) http://www.ScheduleWorld.com/tg/ WebDAV: http://www.ScheduleWorld.com/sw/webDAVDir/4000.ics VFREEBUSY: http://www.ScheduleWorld.com/sw/freebusy/4000.ifb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
