tlyuhas wrote: > I think I might be approaching this all wrong. With the gdata api and > all the docs, I can see how it's possible to read/write/etc a google > calendar and that's what most people want to do. I just want to > create an authenticated session so that I can download the basic.ics > as a file. So when I have a non-public (but shared with me) calendar > like: http://www.google.com/calendar/ical/dude%40nowhere.ex/public/basic.ics > which requires me to authenticate, I want to be able to authenticate a > session and then just download that file in its entirety without > parsing it as a feed. > > These will go to another calendar program which handles ics files. >
Using either an API or protocol calls, 1) Authenticate with client login http://code.google.com/apis/calendar/developers_guide_protocol.html#AuthClientLogin. 2) Make a get request for the url that you have noted, passing in the authorization token that you received in step 1) 3) Save the body of the response, or pass it directly to your other calendar program. Since the calendar you are attempting to download in step 2) is shared with you, you will be permitted to use your own username and password to authenticate in step 1). Ray --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
