This is what I plan to do .... When user first installs 'your' app , ask him to login to you site from within the application. When he logg's in , send his unique opensocial id to your login page(say www.example.com/login.php?uid=1231412234&loginname=blahblah&pass=aasd) , and store this id into your users table , in the row which contains the user name from which he logged in.
So , for any successive attempts to view the app , you get his opensocial id , map it to the user name , and show his details . ****But as I see it , with no User authentication by opensocial , anyone can loggin by directly visiting www.example.com/login.php?uid=1231412234&loginname=blahblah&pass=aasd and can map his own 'your site' log in id to someone else's opensocial ID. The folks at Open Id (they say) are working on the Authentication part) *********************OR************* You could implement an Opensocial container to your site . (hard work, I think)..... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial 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/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
