Sorry for replying to old thread. Franck, did you file jira case for this issue?
- Henry On Fri, Dec 10, 2010 at 1:05 AM, franck tankoua <[email protected]> wrote: > ->Yes the "entry" instead of the list is confusing. > so in your example > {{{ > * {"id":"viewerFriends", > "result":{"filtered":false,"totalResults":3,"sorted":false, > > "entry":[{"gender":"male","id":"george.doe","name":{"formatted":"George > Doe","familyName":"Doe","givenName":"George"}}, > {"gender":"female","id":"jane.doe","name":{"formatted":"Jane > Doe","familyName":"Doe","givenName":"Jane"}}, > {"gender":"female","id":"maija.m","name":{"formatted":"Maija > Meikäläinen","familyName":"Meikäläinen","givenName":"Maija"}}], > "updatedSince":false}}, > {"id":"viewerData","result":{"john.doe":{"count":"0"}}}, > {"id":"viewerFriendData","result":{"jane.doe":{"count":"7"},"maija.m":{},"george.doe":{"count":"2"}}} > * > }}} > > -> Also the GroupId in the response (json-rpc) is an object and not an > opaque String or "@self" / "@friends" / "@all" as suggested here > http://opensocial-resources.googlecode.com/svn/spec/1.0/Social-Data.xml#Group-ID > > so instead of receiving : > *... "entry" :{"title":"truc", "description":"desc", > "id":{"groupId":"CoolTeam","type":"groupId"}} ....* > > We should receive > > *... "entry" :{"title":"truc", "description":"desc", "id":"CoolTeam"} ....* > > Thanks > > On Thu, Dec 9, 2010 at 12:38 PM, Paul Lindner <[email protected]> wrote: > >> Can you suggest how the json-rpc response should be different based on the >> spec? >> >> I think the example shows "entry:" instead of "list" is that what's >> confusing? >> >> >> >> [{"id":"viewer","result":{"gender":"male","id":"john.doe","name":{"formatted":"John >> Doe","familyName":"Doe","givenName":"John"}}}, >> {"id":"viewerFriends", >> "result":{"filtered":false,"totalResults":3,"sorted":false, >> >> "list":[{"gender":"male","id":"george.doe","name":{"formatted":"George >> Doe","familyName":"Doe","givenName":"George"}}, >> {"gender":"female","id":"jane.doe","name":{"formatted":"Jane >> Doe","familyName":"Doe","givenName":"Jane"}}, >> {"gender":"female","id":"maija.m","name":{"formatted":"Maija >> Meikäläinen","familyName":"Meikäläinen","givenName":"Maija"}}], >> "updatedSince":false}}, >> {"id":"viewerData","result":{"john.doe":{"count":"0"}}}, >> >> {"id":"viewerFriendData","result":{"jane.doe":{"count":"7"},"maija.m":{},"george.doe":{"count":"2"}}}] >> >> On Thu, Dec 9, 2010 at 8:23 AM, franck tankoua <[email protected]> wrote: >> >> > Hi All, >> > Can someone help me on this please. >> > I have looked at org.apache.shindig.protocol.JsonRpcServlet at the >> > specification is still for 0.9. >> > While reading the release note of the version 2.0.0 I have thought there >> > were an implementation for this. >> > >> > If there is nothing, I could try to work on a patch. >> > >> > Thanks. >> > >> > On Wed, Dec 8, 2010 at 2:05 PM, franck tankoua <[email protected]> >> wrote: >> > >> > > Hi All. >> > > >> > > Any work being done to follow up the specification 1.0 ? >> > > >> > > >> > > >> > >> http://opensocial-resources.googlecode.com/svn/spec/1.0/Core-Data.xml#Collection >> > > >> > > >> > > -- >> > > Franck >> > > >> > >> > >> > >> > -- >> > Franck >> > >> >> >> >> -- >> Paul Lindner -- [email protected] -- linkedin.com/in/plindner >> > > > > -- > Franck
