Alejandro Rivero wrote: > We have a contained with the data of the current service (*acebook) > and we need to gather data from the other (*witter). It makes sense to > gather this data into opensocial data structures, but which should be > the best strategy? Could it be sensible to ask the other service > (*witter) to send us, via JSON, an object of type OpenSocial > Container?
I'm the author of many of the Jaiku widgets including the Facebook app, the iGoogle app, and now the OpenSocial app (http://jaikufans.com/_tools/opensocial/jaiku.xml) Feel free to read the above XML to see how I handle it all. Twitter will give you JSON, so why would you need it in any other form? I'm not sure why it would need (or want) to be in an 'open social data structure'? Once you have the JSON, you can render it. The problem right now is one of authenticated calls .. you can't store the person's auth details in OS right now due to security. So I have a proxy that stores the users' prefs and associates OpenSocial user IDs with Jaiku users and their display preferences. And because of these issues, you can't post to Jaiku without getting the user to re-auth. Cheers! Rick Measham P.S. What's with the *witter and *acebook??? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial API Definition (was 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 -~----------~----~----~----~------~----~------~--~---
