Jesse, Yes, its largely because the implementations are samples. For activities if you take a look at the OpenSocial rest spec the API doesnt define how groups are used so in this case the implementation in Shindig is up to spec. However that doesnt mean that the spec is doing a good job in this area, you can wasily imagine how you could use group to read activities generated / received by a specific audience. Hence they were thrown into Shindig's SPI in anticipation of this being specced out.
- Louis On Wed, Sep 30, 2009 at 7:23 AM, Ciancetta, Jesse E. <[email protected]>wrote: > Hi, > > I'm working on a persistent ActivityService implementation for Java Shindig > and have a question regarding the parameters passed into the interface > methods - how do we know which parameters we're supposed to use and which > ones to ignore? > > I'm looking at the JsonDbOpensocialService and ActivityServiceDb sample > implementations, and it looks like in most of the interface methods the > groupId and appId parameters aren't used for anything. > > Is that only because these are samples and aren't intended to be complete? > Should I be checking to see if they're null or empty, and if not, using > them in the queries to my backend store? > > Thanks! > > --Jesse >
