Re: Clarification regarding JSON RPC response key

[Jacob Gyllenstierna]

Can anyone shed some light on this? Thx.

Shishir Birmiwal wrote:

+shindig-dev


Thanks,
Shishir

On Tue, Dec 30, 2008 at 3:22 PM, Shishir Birmiwal <birmi...@google.com>wrote:

Also, at json-rpc spec specifies this to be "result" (
http://groups.google.com/group/json-rpc/web/json-rpc-1-2-proposal?pli=1)

Thanks,
Shishir


On Mon, Dec 29, 2008 at 12:31 PM, Shishir Birmiwal <birmi...@google.com>wrote:

Hello,

As per JSON RPC spec (
http://www.opensocial.org/Technical-Resources/opensocial-spec-v081/rpc-protocol),
the result of a RPC request is contained in the key "*result*" (see
example from the spec below). However, code in shindig (
http://svn.apache.org/repos/asf/incubator/shindig/trunk/java/social-api/src/main/java/org/apache/shindig/social/opensocial/service/JsonRpcServlet.java:
 getJsonResponse(..) ) sets the key "
*data*" with the result of the query.

What should be the right field to populate the result with?

*Example from the spec*
{
   "id" : "myself"
   "*result*" : {
     "id" : "example.org:34KJDCSKJN2HHF0DW20394",
     "name" : { "unstructured" : "Jane Doe"},
     "gender" : "female"
  }
}

Thanks,
Shishir

--

Margaret Mead  - "Always remember that you are absolutely unique. Just
like everyone else."

--

Fran Lebowitz  - "My favorite animal is steak."

--
Jacob Gyllenstierna

smime.p7s
Description: S/MIME Cryptographic Signature