Hi Mahesh, The SPI is essentially a service provider interface that allows you to implement OpenSocial on your own website. It is being released via an open source Apache project known as Shindig. We are expecting to have some initial code available for this by the end of the week or early next week.
You can find some background information on Shindig here in this previous OpenSocial blog post. http://opensocialapis.blogspot.com/2007/11/thoughts-on-implementing-opensocial-for.html Hope this helps, -Chris On Dec 9, 8:17 pm, Mahesh Prasad <[EMAIL PROTECTED]> wrote: > There isn't sufficient information about what is needed on the server > side to host Open Social Apps. Open Social API documentation seems to > mainly deal with the client side. > > Am I right in assuming that on the server side I can implement any > logic to retrieve user data; but as long as I expose standard URL > endpoints (for ex: http://{domain}/feeds/people/ for People Data API) > and return data in expected XML format, as described by the > documentation, the server can interact successfully with the Open > Social Gadgets? > > Or is there more to it? And what is SPI? > > Thanks > Mahesh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" 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-container?hl=en -~----------~----~----~----~------~----~------~--~---
