Partuza is a 'demo container' project of mine to show how to implement PHP Shindig in an social network site, and to allow gadget developers to run a local SNS to develop & test their gadgets on.
So while it doesn't have all the bits and things you would expect in a full blown SNS (it doesn't have photos, messages, paging, etc) it does support pretty much all the open social features that exist, and runs the latest (php) shindig development code. You can find a live demo version of it at : http://www.partuza.nl It supports anonymous (json and atom) basic REST calls, however full atom input format support & multipart/mixed batching support are still under development and i expect to have a initial working version live in a couple of days. Some examples: Fetch person in json format: http://modules.partuza.nl/social/rest/people/1/@self Same in atom format: http://modules.partuza.nl/social/rest/people/1/@self?format=atom Fetch friends in json format: http://modules.partuza.nl/social/rest/people/1/@friends Atom: http://modules.partuza.nl/social/rest/people/1/@friends?format=atom My horoscope appdata: http://modules.partuza.nl/social/rest/appdata/1/@self/82 The same in atom: http://modules.partuza.nl/social/rest/appdata/1/@self/82?format=atom Activities in json: http://modules.partuza.nl/social/rest/activities/1/@friends And of course atom: http://modules.partuza.nl/social/rest/activities/1/@friends?format=atom It's still a bit early, the REST interface won't be rocking until the complete atom and batching support is done, but if you want an early sneak preview, there it is :) -- Chris On Jul 18, 2008, at 10:49 PM, Davi Sáránszky Mesquita wrote: > Where? Which container? > > On Fri, Jul 18, 2008 at 4:41 PM, Chris Chabot <[EMAIL PROTECTED]> > wrote: > Almost, give it a few more days and i'll have a first demo > environment up to play with > > On Jul 18, 2008, at 6:44 PM, anand sharma wrote: > >> Hii to All >> >> is there any RESTFUL API specification on PHP side ? >> >> and how to use that Restful api to fetch all people or >> friends etc. >> >> thx all. >> >> cheers >> >> Anand >> >> >> On Fri, Jul 18, 2008 at 6:43 PM, Tamir <[EMAIL PROTECTED]> >> wrote: >> >> Hi, >> I'm trying to understand the structure of url's of resource request >> in >> the RESTful API Specification. >> >> >From the following three example: >> /people/{guid}/@all -- Collection of all people >> connected to user {guid} >> /people/{guid}/@friends -- Collection of all >> friends of user {guid}; subset of @all >> /people/{guid}/{groupid} -- Collection of all people >> connected to user {guid} in group {groupid} >> >> I understand that the structure is [resourceType]/[Unique >> Identifier]/ >> [Criteria] >> But the fourth example is not clear for me: >> /people/{guid}/@all/{pid} -- Individual person record >> for a specific person known to {guid}; shows {guid}'s view of {pid}. >> >> what is the different between "/people/{guid}/@all/{pid}" and "/ >> people/{pid}/@self"? >> when should I use "/people/{guid}/@all/{pid}"? >> >> Cheers >> >> Tamir Zaslavsky >> DiffDoof >> >> >> >> >> > > > > > > > -- > Atenciosamente > > Davi Sáránszky Mesquita > +55-11-81809411 > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
