TZ is my shorthand for TimeZone. :] Sorry about that. I don't think it's so much a client or server side issue as it is a documentation issue. If it were server side I think they'd be having the same problems with the web face. I think. It's quite possible they are bypassing their own service in their interface.
Mine were 6 hours behind. I haven't tested this fully yet (and I haven't been able to work on it in a week), but these are the scenarios I've thought of: o The whole service requires times input as Zulu with an offset (e.g., 14:00:00Z-06:00). o The individual calendar requires times input in the same time zone as the calendar is defined (e.g., Calendar is in PST, time needs to be 08:00:00PST) o Same as above, but with an offset (e.g., 08:00:00PST-00:00) The first two haven't seemed to work, I'll try this last one sometime this week unless I get clarification. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
