Following on from the discussion link below: http://groups.google.com/group/google-calendar-help-dataapi/browse_thread/thread/939c1d87e6f3c69d/83d5ff9164b559be?hl=en&lnk=gst&q=sub++calendars#83d5ff9164b559be
Is it right that when using the (Zend Framework) insertEvent() method to write a calendar event to a 'sub' calendar (not the account's 'principle' default calendar), that the private address that is supplied as the second argument _shouldn't_ contain the full address provided by the Google calendar settings 'Private Address: XML' option? In fact if I use this as-is it won't even write the event to the calendar?? It seems all I need is the first part of this address, with the end part that contains '/private-abcdef12345some-big-long- magic-number/basic' needing to be stripped. This is fine but what I'm not understanding is surely this big-long-magic-number is the bit that is providing the security? If anyone can just use the same address as is provided for the public address, but with '/private/full' tagged on the end, and have full calendar [write] access, then this is compromises the calendar's security? And why isn't the big-long-magic- number used also for this? http://www.google.com/calendar/feeds/<general [sub]-calendar address> %40group.calendar.google.com/private/full I've probably missed something somewhere, so any help on this would be appreciated! Regards, Harvey. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
