Looking forward to it. As always, send a note to the list if you run into trouble, or would like help w/ the code review process.
Speaking of this, it's often nice to manage a project like this via the JIRA issue tracker: http://issues.apache.org/jira/browse/SHINDIG Your mileage may vary. --j On Thu, Jul 8, 2010 at 12:05 PM, Gabriel Guardincerri <gguar...@gmail.com>wrote: > Awesome, great info! > > On Wed, Jul 7, 2010 at 8:12 PM, John Hjelmstad <fa...@google.com> wrote: > > > Hi Gabriel: > > > > Great to hear! As luck would have it, Charles Severance recently wrote up > > some documentation on how to add a new API to the social-api server here: > > > > > http://www.dr-chuck.com/csev-blog/2010/07/playing-with-shindigopensocial-adding-a-new-feature-and-a-service/ > > > > I suspect this will provide a nice bootstrap for your needs, in concert > w/ > > the spec itself. Parameter name "body" should give you access to the > > request > > body, from [Social]RequestItem.getParameter(...). > > > > As for the implementation itself, perhaps this is obvious but I'd suggest > > something like: > > 1. Introduce base interface for persistence ie. > > ContentUpload[Persistence|Service], with operations read(...) and > > write(...), in: > > > > > http://svn.apache.org/repos/asf/shindig/trunk/java/social-api/src/main/java/org/apache/shindig/social/opensocial/spi/ > > 2. Introduce default implementation (eg. filesystem-based) for #1. > > 3. Write ContentUploadHandler in: > > > > > http://svn.apache.org/repos/asf/shindig/trunk/java/social-api/src/main/java/org/apache/shindig/social/opensocial/service/ > > , > > with persistence @Inject'ed > > - Implements the real semantics of the API per spec. > > 4. Don't enable use of the default handler (#2) by default; you don't > want > > to enable new functionality that uses nontrival hardware resources w/o > > service providers being aware. Instead document the default handler (for > > testing) and indicate how a custom such handler may be supported. > > > > Cheers, > > John > > > > On Wed, Jul 7, 2010 at 2:33 PM, Gabriel Guardincerri <gguar...@gmail.com > > >wrote: > > > > > Hi John, > > > > > > I'm going to start adding this feature to shindig, I will be working > with > > > the Java version. Any start points/advices about this? > > > > > > Thanks > > > > > > Gabriel > > > > > > On Thu, Jul 1, 2010 at 10:56 AM, Gabriel Guardincerri < > > gguar...@gmail.com > > > >wrote: > > > > > > > Hi John, > > > > > > > > I'm interested in having that feature, so I could probably contribute > > to > > > > Shindig instead of making a workaround. Do you have an idea of how > hard > > > > would it be to add this to Shindig? > > > > > > > > Thanks, > > > > > > > > Gabriel > > > > > > > > > > > > On Wed, Jun 30, 2010 at 1:31 PM, John Hjelmstad <fa...@google.com> > > > wrote: > > > > > > > >> Hi Gabriel: > > > >> > > > >> afaik you're not missing anything. This part of the opensocial 1.0 > > > >> spec isn't implemented in Shindig yet. We'd be happy to accept > > > >> contributions. Do you use php, java, or both? > > > >> > > > >> John > > > >> > > > >> On Wednesday, June 30, 2010, Gabriel Guardincerri < > gguar...@gmail.com > > > > > > >> wrote: > > > >> > Hi, > > > >> > > > > >> > I'm not sure if this is the right list to post this questions, but > > it > > > >> seems > > > >> > to be the more active. Please let me know if I need to post it in > > > >> another > > > >> > list. > > > >> > > > > >> > I'm using Shindig and I would like to be able to store files, > things > > > >> like > > > >> > images, videos, word documents, etc. I've tried to do that but it > > > seems > > > >> to > > > >> > the REST services don't support headers with content types like: > > > >> > > > > >> > Content-Type: image/gif > > > >> > Content-type: multipart/form-data > > > >> > > > > >> > On the other side it seems that Opensocial Spec > > > >> > > > > >> > > > > > > http://opensocial-resources.googlecode.com/svn/spec/1.0/Core-API-Server.xml#Content-Uploadhas > > > >> > a spec for doing that. > > > >> > > > > >> > So, am I missing something? If not, is this going to be supported > or > > > >> there a > > > >> > way to extend Shindig to support this? > > > >> > > > > >> > Thanks in advance, > > > >> > > > > >> > Gabriel > > > >> > > > > >> > > > > > > > > > > > > > >
