On Mon, Jan 19, 2009 at 1:12 AM, Rajdeep Dua <[email protected]> wrote: > I have compiled a presentation based on Sun's Social Site project which > extends Shindig into a full blown SNS. > > http://sites.google.com/site/opensocialarticles/social-site-architecture
Nice! You've got a pretty good overview of SocialSite internals there. I've got a couple of corrections for you. Most of them stem from the fact that your presentation confuses the SocialSite Server with the sample app that we include to show how to use our gadgets. We've been working to reduce this confusion and if you look at our current code base, you'll see that there is now a very clear separation between the server and the sample app(s). The point is that SocialSite is a centralized social graph server that provides access to the graph data via web services (OpenSocial + extensions) and infrastructure for running authenticated OpenSocial Gadgets on any type of web site. The only UI we offer is in the form of OpenSocial Gadgets and an admin console (not for end users). The sample app is just one example of how our Gadgets can be used. Here are some specific corrections/notes on the presentation: Page 2 - Note that Struts/Tiles are used in only two places 1) the Admin Console 2) A sample app that shows how to use our gadgets with Struts/Tiles Page 3 - Again: Struts/Tiles only in Admin Console Page 4 - This is a screen-shot of the Struts/Tiles sample app Page 5 - Pages from the Struts/Tiles sample app Page 7 - We no longer package as JMaki widgets, we're pure OpenSocial Gadgets now and you can add our gadgets with just couple of lines of JavaScript - Gadgetizer is a gadget that can display a collection of gadgets, managed by the user Page 18 - Should mention that Profile properties are defined by a configuration file, so you can leave out standard properties or you can add new properties specific to your social site. Hope that helps... Thanks, Dave
