Bhavesh,

Storing session token is a good design consideration in order to not
always ask the user to login to GH everytime he/she has to do
something on his profile.

On Wed, Dec 16, 2009 at 4:27 PM, Bhavesh Singh <[email protected]> wrote:
> Thank you all for your valuable advice.
> What I don't understand is what information do I store on my server to
> identify each user uniquely and how do I  retrieve or update information
> asynchronously. Do i need to store the token strings for each user and use
> it every time I want to update a user's profile.
> I tried that but a GDataException is raised when I supply previously saved
> token strings.
>
> On Tue, Dec 15, 2009 at 4:04 PM, Bess Ho <[email protected]> wrote:
>>
>> You can access entire CCR record using localhost. Yes you can access user
>> data in each profile. However you would have to parse each record to access
>> to specific data.
>>
>> User would have to grant permission to read the data via OAuth or AuthSub.
>> It's all private data.
>>
>> This may help you to understand what and how you can read on user profile.
>>
>> http://www.slideshare.net/bess.ho/google-health-architecture-api
>>
>> On Mon, Dec 14, 2009 at 1:32 AM, Bhavesh Singh <[email protected]>
>> wrote:
>>>
>>> Hi,
>>> I'm an engineering student and doin a project on accessing and
>>> updating the profiles of the users of Google Health.
>>> I went through the code samples.
>>> What confused me was that how do i access a user's profile once he has
>>> given consent to my accessing it. I'm using the "localhost" as the url
>>> to which the user is redirected. Does Google provide us with any data
>>> that is unique for each user and we can access his profile without
>>> having him logon and provide consent to access (that's what the code
>>> does!)
>>> I would be grateful if someone could really come forward and clear my
>>> perspective.
>>>
>>> Thanks.
>>> Bhavesh Singh.
>>> Sinhgad Institute of Technology, India.
>>>
>>> --
>>>
>>> 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.
>>>
>>>
>>
>>
>>
>> --
>> Bess Ho
>> UI Architect / Developer / Designer
>> iPhone Developer
>> Silicon Valley Web Builder (SVWB) Founder
>>
>> The information transmitted is intended only for the person or entity to
>> which it is addressed and may contain CONFIDENTIAL material. If you receive
>> this material/information in error, please contact the sender and delete or
>> destroy the material/information.
>>
>> --
>>
>> 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.
>
> --
>
> 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.
>



-- 
Emmanuel F. Caulin
Makati City, Philippines

--

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.


Reply via email to