You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Shishir Birmiwal <bi...@google.com> on 2009/01/12 06:01:30 UTC
Re: Clarification regarding JSON RPC response key
+shindig-dev
Thanks,
Shishir
On Tue, Dec 30, 2008 at 3:22 PM, Shishir Birmiwal <bi...@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 <bi...@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."
Re: [opensocial-and-gadgets-spec] Re: Clarification regarding JSON
RPC response key
Posted by Jacob Gyllenstierna <ja...@enemyunknown.net>.
One idea is to have one URL that returns 'data' and another that returns
'result'. That way developers can both use the Google Code clients as
well as clients that conform to the spec.
Sachin Shenoy wrote:
> Can we make the behavior in shindig configurable and let each container do
> the work required for its transition?
> Sachin
>
>
> On Fri, May 15, 2009 at 11:12 PM, Lane LiaBraaten <ll...@google.com>wrote:
>
>> Do you think it's feasible to support both for a short time during the
>> transistion? i.e. include the same content in the 'data' and 'result'
>> property? I'm not sure how large these request bodies normally are, but if
>> they're small it seems like this would help with the transition.
>>
>> -Lane
>>
>>
>> On Thu, May 14, 2009 at 4:04 AM, Chris Chabot <ch...@google.com> wrote:
>>
>>> Ow, all the client libraries use the data key as well. We should make sure
>>> to ping those folks too when we do the big switcheroo
>>>
>>>
>>> On Thu, May 14, 2009 at 3:56 AM, Louis Ryan <lr...@google.com> wrote:
>>>
>>>> Unfortunately Shindig has been using "data" for quite some time and we
>>>> need to figure how to transition over without breaking lots of folks.
>>>>
>>>>
>>>> On Wed, May 13, 2009 at 3:02 PM, Lane LiaBraaten <ll...@google.com>wrote:
>>>>
>>>>> It should be 'result' - OpenSocial follows the RPC spec that Shishir
>>>>> linked to.
>>>>>
>>>>> -Lane
>>>>>
>>>>>
>>>>> On Wed, May 13, 2009 at 1:01 PM, Jacob Gyllenstierna <
>>>>> jacob@enemyunknown.net> wrote:
>>>>>
>>>>>> 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 <
>>>>>>> birmiwal@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 <
>>>>>>>> birmiwal@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
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>> --~--~---------~--~----~------------~-------~--~----~
>> You received this message because you are subscribed to the Google Groups
>> "OpenSocial and Gadgets Specification Discussion" group.
>> To post to this group, send email to
>> opensocial-and-gadgets-spec@googlegroups.com
>> To unsubscribe from this group, send email to
>> opensocial-and-gadgets-spec+unsubscribe@googlegroups.com<op...@googlegroups.com>
>> For more options, visit this group at
>> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en
>> -~----------~----~----~----~------~----~------~--~---
>>
>>
>
--
Jacob Gyllenstierna
Product Manager, Developer Platform
Avatars United – Improve Your Virtual Life
www.avatarsunited.com
Enemy Unknown AB
Phone [ +46 (0)707 508801 ]
E-mail [ jacob@enemyunknown.net ]
Skype [ p0rkins ]
Re: [opensocial-and-gadgets-spec] Re: Clarification regarding JSON
RPC response key
Posted by Sachin Shenoy <th...@gmail.com>.
Can we make the behavior in shindig configurable and let each container do
the work required for its transition?
Sachin
On Fri, May 15, 2009 at 11:12 PM, Lane LiaBraaten <ll...@google.com>wrote:
> Do you think it's feasible to support both for a short time during the
> transistion? i.e. include the same content in the 'data' and 'result'
> property? I'm not sure how large these request bodies normally are, but if
> they're small it seems like this would help with the transition.
>
> -Lane
>
>
> On Thu, May 14, 2009 at 4:04 AM, Chris Chabot <ch...@google.com> wrote:
>
>> Ow, all the client libraries use the data key as well. We should make sure
>> to ping those folks too when we do the big switcheroo
>>
>>
>> On Thu, May 14, 2009 at 3:56 AM, Louis Ryan <lr...@google.com> wrote:
>>
>>> Unfortunately Shindig has been using "data" for quite some time and we
>>> need to figure how to transition over without breaking lots of folks.
>>>
>>>
>>> On Wed, May 13, 2009 at 3:02 PM, Lane LiaBraaten <ll...@google.com>wrote:
>>>
>>>> It should be 'result' - OpenSocial follows the RPC spec that Shishir
>>>> linked to.
>>>>
>>>> -Lane
>>>>
>>>>
>>>> On Wed, May 13, 2009 at 1:01 PM, Jacob Gyllenstierna <
>>>> jacob@enemyunknown.net> wrote:
>>>>
>>>>> 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 <
>>>>>> birmiwal@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 <
>>>>>>> birmiwal@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
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "OpenSocial and Gadgets Specification Discussion" group.
> To post to this group, send email to
> opensocial-and-gadgets-spec@googlegroups.com
> To unsubscribe from this group, send email to
> opensocial-and-gadgets-spec+unsubscribe@googlegroups.com<op...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
Re: [opensocial-and-gadgets-spec] Re: Clarification regarding JSON
RPC response key
Posted by Lane LiaBraaten <ll...@google.com>.
Do you think it's feasible to support both for a short time during the
transistion? i.e. include the same content in the 'data' and 'result'
property? I'm not sure how large these request bodies normally are, but if
they're small it seems like this would help with the transition.
-Lane
On Thu, May 14, 2009 at 4:04 AM, Chris Chabot <ch...@google.com> wrote:
> Ow, all the client libraries use the data key as well. We should make sure
> to ping those folks too when we do the big switcheroo
>
>
> On Thu, May 14, 2009 at 3:56 AM, Louis Ryan <lr...@google.com> wrote:
>
>> Unfortunately Shindig has been using "data" for quite some time and we
>> need to figure how to transition over without breaking lots of folks.
>>
>>
>> On Wed, May 13, 2009 at 3:02 PM, Lane LiaBraaten <ll...@google.com>wrote:
>>
>>> It should be 'result' - OpenSocial follows the RPC spec that Shishir
>>> linked to.
>>>
>>> -Lane
>>>
>>>
>>> On Wed, May 13, 2009 at 1:01 PM, Jacob Gyllenstierna <
>>> jacob@enemyunknown.net> wrote:
>>>
>>>> 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 <birmiwal@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 <
>>>>>> birmiwal@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
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "OpenSocial and Gadgets Specification Discussion" group.
> To post to this group, send email to
> opensocial-and-gadgets-spec@googlegroups.com
> To unsubscribe from this group, send email to
> opensocial-and-gadgets-spec+unsubscribe@googlegroups.com<op...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
Re: [opensocial-and-gadgets-spec] Re: Clarification regarding JSON
RPC response key
Posted by Chris Chabot <ch...@google.com>.
Ow, all the client libraries use the data key as well. We should make sure
to ping those folks too when we do the big switcheroo
On Thu, May 14, 2009 at 3:56 AM, Louis Ryan <lr...@google.com> wrote:
> Unfortunately Shindig has been using "data" for quite some time and we need
> to figure how to transition over without breaking lots of folks.
>
>
> On Wed, May 13, 2009 at 3:02 PM, Lane LiaBraaten <ll...@google.com>wrote:
>
>> It should be 'result' - OpenSocial follows the RPC spec that Shishir
>> linked to.
>>
>> -Lane
>>
>>
>> On Wed, May 13, 2009 at 1:01 PM, Jacob Gyllenstierna <
>> jacob@enemyunknown.net> wrote:
>>
>>> 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 <birmiwal@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 <
>>>>> birmiwal@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
>>>
>>
>>
>>
>>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "OpenSocial and Gadgets Specification Discussion" group.
> To post to this group, send email to
> opensocial-and-gadgets-spec@googlegroups.com
> To unsubscribe from this group, send email to
> opensocial-and-gadgets-spec+unsubscribe@googlegroups.com<op...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
Re: [opensocial-and-gadgets-spec] Re: Clarification regarding JSON
RPC response key
Posted by Louis Ryan <lr...@google.com>.
Unfortunately Shindig has been using "data" for quite some time and we need
to figure how to transition over without breaking lots of folks.
On Wed, May 13, 2009 at 3:02 PM, Lane LiaBraaten <ll...@google.com>wrote:
> It should be 'result' - OpenSocial follows the RPC spec that Shishir linked
> to.
>
> -Lane
>
>
> On Wed, May 13, 2009 at 1:01 PM, Jacob Gyllenstierna <
> jacob@enemyunknown.net> wrote:
>
>> 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 <birmiwal@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 <birmiwal@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
>>
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "OpenSocial and Gadgets Specification Discussion" group.
> To post to this group, send email to
> opensocial-and-gadgets-spec@googlegroups.com
> To unsubscribe from this group, send email to
> opensocial-and-gadgets-spec+unsubscribe@googlegroups.com<op...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
Re: Clarification regarding JSON RPC response key
Posted by Lane LiaBraaten <ll...@google.com>.
It should be 'result' - OpenSocial follows the RPC spec that Shishir linked
to.
-Lane
On Wed, May 13, 2009 at 1:01 PM, Jacob Gyllenstierna <jacob@enemyunknown.net
> wrote:
> 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 <birmiwal@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 <birmiwal@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
>
Re: Clarification regarding JSON RPC response key
Posted by Jacob Gyllenstierna <ja...@enemyunknown.net>.
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 <bi...@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 <bi...@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