From photark-dev-return-1229-apmail-incubator-photark-dev-archive=incubator.apache.org@incubator.apache.org Thu Feb 03 02:47:09 2011 Return-Path: Delivered-To: apmail-incubator-photark-dev-archive@minotaur.apache.org Received: (qmail 72647 invoked from network); 3 Feb 2011 02:47:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Feb 2011 02:47:09 -0000 Received: (qmail 53321 invoked by uid 500); 3 Feb 2011 02:47:09 -0000 Delivered-To: apmail-incubator-photark-dev-archive@incubator.apache.org Received: (qmail 53283 invoked by uid 500); 3 Feb 2011 02:47:08 -0000 Mailing-List: contact photark-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: photark-dev@incubator.apache.org Delivered-To: mailing list photark-dev@incubator.apache.org Received: (qmail 53275 invoked by uid 99); 3 Feb 2011 02:47:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Feb 2011 02:47:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of umashanthip@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-gw0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Feb 2011 02:47:01 +0000 Received: by gwaa12 with SMTP id a12so299887gwa.6 for ; Wed, 02 Feb 2011 18:46:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=6hoa0QFQwtMMxTSYpfUwTgQXvfnL3Gwd+vtIrrLnJh4=; b=p1jDccE2YBvq3teHYiqy9m6PiicrGUMZmowd8bwUnQG91PfNSaXaKBk/u1ibTj5o44 xr2lIFfhpBjt3prLh5b7GQq6Gv5EfUxFGCx04j0JeRbCPvX0hHSM3ue2joiNupOiWt/g TxpeAtvhtSxtoyv6jIrZRw+1BJkvppNuDqXUo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=IYmK+qNbx5RluGkxtIjSb92d+U83suGUoXSH8uoJwRBMvj88LIMfJwcrIPnhDaxylz kC87+6pOVWBfXCPk0XUXRbU/4W0KE+wRHbW+C1U9nvpC41u7j42l4gFvMG19VW5LRbt2 QbNuEaIAyxFKMGyoHirovpVbwODeaMog2FSao= MIME-Version: 1.0 Received: by 10.101.17.11 with SMTP id u11mr4560740ani.186.1296701200360; Wed, 02 Feb 2011 18:46:40 -0800 (PST) Received: by 10.100.94.4 with HTTP; Wed, 2 Feb 2011 18:46:40 -0800 (PST) In-Reply-To: References: Date: Thu, 3 Feb 2011 08:16:40 +0530 Message-ID: Subject: Re: Making PhotArk More Social From: Umashanthi Pavalanathan To: photark-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=00504501706a6d6d68049b57c62f X-Virus-Checked: Checked by ClamAV on apache.org --00504501706a6d6d68049b57c62f Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jan 27, 2011 at 4:43 AM, Umashanthi Pavalanathan < umashanthip@gmail.com> wrote: > Hi, > > On Mon, Jan 24, 2011 at 11:55 AM, Umashanthi Pavalanathan < > umashanthip@gmail.com> wrote: > >> >> >> On Mon, Jan 24, 2011 at 11:31 AM, Luciano Resende wrote: >> >>> On Sun, Jan 23, 2011 at 9:21 PM, Umashanthi Pavalanathan >>> 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. >> > > As the first step to integrate open social features into PhotArk using > Apache Shindig, it is required to build a social network back-end with > PhotArk and later it can be connected to the Shindig's Service Provider > Interfaces (SPI) [1]. > > In my opinion it is better to design an API for this social network > back-end, so that it can easily be expanded and new requirements in future > open social specifications can be incorporated easily. Basically there > should the following concepts in the API: > 1. Person (user) > 2. User Profiles > 3. Relationship (eg: friends) > 4. User Groups > 5. Activity (user activities including uploading new photos, creating new > albums, commenting, tagging etc) > 6. AppData > 7. Messages > > Shindig Java docs for the package org.apache.shindig.social and it's sub > packages available at [2] would give more idea of such API. > If you agree with this approach, I would like to start building a Social > API for PhotArk and discuss more here. > Any thoughts regarding this idea of creating an API for the social features? Would like to hear your thoughts... Thanks, ~Umashanthi > > Thoughts please? > > [1] http://www.opensocial.org/page/building-an-opensocial > [2] http://shindig.apache.org/shindig-1.1.x/apidocs/index.html > > Thanks, > ~Umashanthi > > > >> >> >> [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/ >>> >> >> > --00504501706a6d6d68049b57c62f--