Hi there,

Your understanding is correct, you can not get with the current
production API any unique user ID. With Open Social, yes, this is
expected to be possible, but Open Social is not in production on
iGoogle yet, and we still have to hear from a target date for this
functionality to go live.

If you need to uniquely identify a gadget instance, the usual solution
is to store a unique ID in the gadget preferences as a hidden pref.
The first time the gadget runs, the code would notice that the hidden
pref has its default value, and would initiate a fetch request to your
server to obtain a new unique ID. You would then store this unique ID
in the hidden pref, and you have a permanent ID for this specific
gadget instance at that point.

This is not perfect, as if the users removes the gadget and add it
back, you will not  be able to make the link and it would just look
like a new user to you. You would also not be able to realize that if
the user adds multiple gadget instances on the same iGoogle account
(on different tabs for instance), here again you would not know the
different instances are from the same user.

I hope this helps.

Jerome

On Feb 20, 9:51 am, "[email protected]" <[email protected]> wrote:
> Hi
>
> I made for my company a gadget that needs to recover the google ID of
> the user, so it uses it as a token to sign in our platform. I saw that
> it is possible with opensocial and gadgets.util.* . But, unfortunately
> I have discovered that they have not been in production yet.
> Is there any way to perform this using the legacy API? Is there any
> version of opensocial in production now, or that will be soon?
>
> Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iGoogle Developer Forum" 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-Gadgets-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to