On Mon, Jan 24, 2011 at 11:31 AM, Luciano Resende <luckbr1...@gmail.com>wrote:
> On Sun, Jan 23, 2011 at 9:21 PM, Umashanthi Pavalanathan > <umashant...@gmail.com> wrote: > >> We have been working on a new REST api a branch, and maybe > >> we could start prototyping some OpenSocial integration on top of that. > >> Your help and contributions would be appreciated. > >> > > > > I will start by looking at the REST api branch and the code base. > > > > > > If we use a Open Social framework such as Shindig, does it require a > RDBMS as it's persistence repository (e.g Derby, MySQL)... or can it > be integrated with a JCR repository ? > Well. Simple answer is, the integration is independent of the persistence mechanism. No such requirements from Shindig and we can use the JCR repository or any other database. Small explanation: Apache Shindig[1] provides the following Service interfaces, for the basic OpenSocial concepts[3]: Person Service Activity Service AppData Service Message Service and handlers for each of them. When integrating with Shindig, what we have to do is to write our custom services and handlers (if required) implementing the Shindig services and bind them using guice. So, Shindig doesn't handle the back-end persistence. We can use our own data storage mechanisms and customize the Services provided by Shindig. [1] http://shindig.apache.org/ [2] http://shindig.apache.org/overview.html [3] http://svn.apache.org/repos/asf/shindig/trunk/java/social-api/src/main/java/org/apache/shindig/social/opensocial/ Thanks, ~Umashanthi > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
