Given the fact that no existing code (gadgets or REST clients) use groups at the moment nor are any likely to be created since none of the large networks really support it, so it could be worth skipping over it.
If however it's a requirement for internal usage / your own gadget development & you wanted to implement this, you would start by adding the groups route to shindig/php/src/social/servlet/ApiServlet.php in the handleRequestItem() function, create a GroupService & GroupHandler classes (using the existing people/appdata/activity/media/etc ones as an example of how to do this), adding a configuration key for the groups handler, and then implement the class interface you've just created in your back-end. The amount of code involved really isn't to bad, it's the interpreting of the somewhat vague groups descriptions in the spec that's the tricky part. On Sat, Sep 19, 2009 at 2:58 PM, Fayland Lam <[email protected]> wrote: > Thanks for your clarification, just my leader wants me to do that but > I don't know how. > > Thanks. > > On Sat, Sep 19, 2009 at 8:54 PM, Chris Chabot <[email protected]> wrote: > > Hey Fayland, > > > > On Tue, Sep 15, 2009 at 3:49 AM, Fayland Lam <[email protected]> wrote: > >> > >> 2: what's the "/social/rest/groups/{guid}"? is the group something like > "a > >> group people share the same interesting"? or it is just @me, @self? > > > > 3: is /socila/rest/groups/{guid} done in shindig? and in partuza? which > >> function? > >> > > > > Groups at the moment isn't supported in php shindig & partuza (neither is > it > > in the java version if I'm not mistaking), it's not really in use on any > > live social sites nor is the expected behavior and functioning very well > > documented; So while the spec does hint that it could be, it just really > > isn't in practice. > > > > If it's something you deeply care about, we'd welcome any patches and/or > > spec suggestions. > > > > -- Chris > > > > > > -- > Fayland Lam // http://www.fayland.org/ >
