We really need a FAQ for this question for potential container owners. There's more to it than just the SPI or Data APIs. With a nod to Paul Lindner:-
Join all the mailing lists. You're currently working blind because documentation and code are in flux. Server side: - Implement a FOAF Data API. It will stand you in good stead for when the Data APIs finalise - Start building Atom/gData support based on the docs so far available - OAuth support (likely to be the auth standard for apps) now at V1.0 - OpenID (likely to be the auth standard for people) now at V2.0. Investigate supporting OpenID Attribute Exchange - JSONP support (just because it makes it easy to pull data into JS) - Create a generic persistence layer to store data for apps. This can simply be a serialized map in a database blob on a per app/user basis - Consider how you will validate applications to run on your platform i.e. will you allow any app (via a URL ref) or will you build your own gallery - Create a table to store applications that the user has installed, and where to put them. Let the user add/update/remove apps. - Create a canvas page module and a module for displaying a gadget on a profile page. - Experiment with the first SPI code from Google and Hi5 Client side: - Read and understand how Google Gadgets functions. - Read up on IFRAME communication mechanisms. Note, they are all gross hacks. - Get really familiar with OO JavaScript - Install Firebug, unless you like clicking on alert boxes all day and night. JB Chris Schalk <[EMAIL PROTECTED]> Mon, 10 Dec 2007 16:58:25 > >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-open >social-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 >> -- Julian Bond E&MSN: julian_bond at voidstar.com M: +44 (0)77 5907 2173 Webmaster: http://www.ecademy.com/ T: +44 (0)192 0412 433 Personal WebLog: http://www.voidstar.com/ skype:julian.bond?chat Just Because You Aren't Paranoid, Doesn't Mean They're Not Out To Get You --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
