Your gadget could have a Login state, in which the user
authenticates.  Thinking more about it im not sure of the availability
of cookies, but perhaps you could set the user's authenticated key as
a user_pref. You could skip the login state if the user_pref is set
and the key is valid, this would assist in making the gadget more
accessible as a login state does add another hurdle to leap.





On Sep 8, 3:55 pm, "Dan (Google Employee)" <[EMAIL PROTECTED]> wrote:
> Hi CDM,
>
> With the existing production API, there isn't much you can do, without
> inconveniencing your users. For instance, if you're willing to create
> a user account for each of your users, you can associate an account
> with a specific API key that you include when fetching dynamic
> content. On your server, check for the existence of a valid key before
> returning data.
>
> With the newer version of the API, currently in the sandbox, you can
> have requests originating from iGoogle signed by iGoogle, with the
> gadget URL and the ID of the user making the request. With this data,
> you can be sure that any requests to your server are coming from only
> your gadget (and optionally, from specific users). Unfortunately, this
> will only work in the sandbox for the near future, so you'll have to
> wait, or implement a workaround as I outlined above.
>
> Best,
> Dan
>
> On Sep 7, 5:45 am, CDM <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > I am working on google gadget. I have quesiton that if someone copy my
> > xml file and create gadge using my xml code then it will work. what
> > can i do to prevent this.
>
> > Other thing i am using IG_Fetchcontent to retreive cynamic content.
> > how I can prevent this url not be accessed except my gadget.
>
> > Please help me in this.
>
>
--~--~---------~--~----~------------~-------~--~----~
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