Hi Jofry, If you're using one of the GData client libraries with ClientLogin, authentication will be handled for you. The only differences in authenticating to H9 and production Health that you may need to be aware of are the "scope" and "service" authentication parameters. If you're programming in Java or .NET, these are automatically set when you use the HealthService or H9Service classes (Java). If you're using one of the base service classes, however (e.g. the Java GoogleService class), then you'll need to set the appropriate scope and service, which can be found at the following location:
http://code.google.com/apis/health/getting_started.html#Differences Paul On Jul 9, 7:50 am, Jofry Sutanto <[email protected]> wrote: > Bump. Anyone? > > On Jul 6, 12:27 am, Jofry Sutanto <[email protected]> wrote: > > > > > I'm currently working with h9 server ATM and I just want to know what > > are the main differences between accessing google health's h9 and the > > actual health server particularly using ClientLogin + GData API. > > As I understand it, a session token must always be included to every > > request to server, but isn't that handled automatically by GData API? > > I can't see the clear difference in accessing those two apart from the > > need of registering my application to Google first. -- 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.
