Yes, you could proxy requests to Google through your own web server and add on some authentication, but I am not sure what the use case is here. I understand that others have reported issues, but I don't actually understand what those issues are.
If you want to make all of the events in a particular calendar available for anyone to view, just make that calendar public. Google will then do all of the work of providing you with an embed-able calendar for your web page, all of the flavors xml, html, ics and json will be available to your users, etc. Are you trying to allow users to create events on this calendar? Otherwise I haven't seen the benefit of doing this and even that seems mitigable with some system of automatically accepting events that you are invited to. What am I missing? Thanks, Ray On Wed, Dec 17, 2008 at 7:49 PM, Elbow Festival <[email protected]> wrote: > > Hi group, I'd like to do something involving many users and events, > and I see that other developers have encountered limits and had > conceptual problems aligning their data with GCalendar. I was > wondering if I could get around these problems by having a (read-only) > google calendar widget embedded in my app page, bound to my own > (hosted by me on my own server) feeds of event data. In other words I > would want my calendar URI (and subsequent feed accesses) to not start > with "http://google.com/calendar/etc/etc/etc";, but instead "http:// > my.server.com/custom/feed/url". Is this possible, and if so, how would > I do it? > > > Thanks! > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
