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

Reply via email to