AuthSub is intended for web applications. ClientLogin is intended for desktop/mobile/installed applications.
AuthSub provides a cleaner interface for web apps. The user is redirected to Google, selects which profile he/she wants to link, and the token encodes that information. Also, session tokens never expire so they're ideal for storing long-term in a db. Lastly, the user's email/password are verified on a google page rather than your own app. Users like that! In the mobile/desktop use case, a browser window may not be available. Therefore, username/password is the only option. We have different feeds to distinguish which kind of access an app is using. It's worth mentioning that we do not publish web applications in the service's directory that are using ClientLogin. A summary of both (+OAuth): http://code.google.com/apis/gdata/auth.html Eric On Mar 11, 6:38 am, hlr <[email protected]> wrote: > Hello, > > I am running in a servlet environment and have looked at the different > feeds > for AuthSub and Client Login. Why is there two different ways? > > Thanks > > Herb Rush --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Health Developers" 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/googlehealthdevelopers?hl=en -~----------~----~----~----~------~----~------~--~---
