The spi corresponds to the features/opensocial-reference/*.js files. The features/opensocial-0.7 js code is a client of the spi. Essentially, in order to implement the opensocial js spec all you need to do is extend the container class and somehow implement all of those methods. Shindig provides an example extension of that class which speaks json back to the server. I hope that helps.
- Cassie On Thu, Apr 24, 2008 at 12:04 AM, Amr Khaled <[EMAIL PROTECTED]> wrote: > How are you all ? > I read the following in the OpenSocial section on Google Code > > > To host OpenSocial apps, your website must implement the OpenSocial API > > Specification <http://code.google.com/apis/opensocial/docs/spec.html>. > In > > most cases, this means that you *connect your own social network's > > backends to the OpenSocial Service Provider Interface (SPI), which is > part > > of Shindig <http://incubator.apache.org/shindig/>, to allow an > OpenSocial > > app to access your site's data.* However, it is possible to use data from > > another social network as well, should you prefer. The SPI implements: > > > > - Adding and removing friends > > - Adding and removing apps > > - Storing activities > > - Retrieving activity streams for self and friends > > - Storing and retrieving per-app and per-app-per-user data > > > > What is meant by the SPI and where it's located in Shindig. > -- > Amr Khaled > Faculty of Computers and Information >
