Hi am63, If that is the case why does Google documentation say otherwise? http://code.google.com/apis/accounts/docs/AuthForInstalledApps.html
"Example scenario In this scenario, you're creating an installed application that communicates with Google's Calendar service. Users of Google Calendar manage their schedules, add, update, or delete events, and share calendar information with other users. For your application, you want to be able display Google Calendar data in your interface and provide tools to manipulate the data." On Apr 6, 4:56 pm, am63 <[email protected]> wrote: > Hi, > > About your post in ssr's thread and this one, the only authentication method > supported by the Javascript gdata library is Authsub (the method used in the > samples). All other methods (ClientLogin, oAuth) are not supported. > > This being said, the token you are mentionning is a browser cookie, so it > shouldn't be a problem ? If you want this cookie to be persistent across > browser launches, update the cookie with an expiration date (the library use > a session only cookie, which is discarded by the browser when it is closed). -- 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://code.google.com/apis/calendar/community/forum.html
