dudu, you shouldn't be prompting or storing usernames and passwords. Even if your intent is benign, such a situation is akin to phishing and is not good practice. Rather, you should look into 3-legged OAuth as a solution.
thanks, nolybab On Aug 11, 5:20 pm, duduzerah <eduardopich...@gmail.com> wrote: > I'm working on a opensocial app, that's run in another server. In > content param of the xml, I pass the url, as the specification said. > > But I discover that, I can't call the javascripts methods to fetch > data, because the app is in another server. > > Am I doing something wrong? Or proxied content can't to do these > things? If no I think I lost 2 weeks working on it... > > Inside my opensocial application, the user do a login in another > system. I would like to associate his login with his orkut id for > example, to next time the user don't need to do a login again. But > with proxied content, i read a lot, and can't find examples doing > that.. > If I would know before, I did't build a proxied content application, > but on the opensocial wikis and forums, there are no detailed > infomation. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" group. To post to this group, send email to opensocial-api@googlegroups.com To unsubscribe from this group, send email to opensocial-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
