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 <[email protected]>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 <[email protected]> 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 <[email protected]> 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 <[email protected]>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 < [email protected]> 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 < [email protected]>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 < [email protected]>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 [email protected] To unsubscribe from this group, send email to [email protected]<opensocial-and-gadgets-spec%[email protected]> 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 [ [email protected] ] Skype [ p0rkins ]
smime.p7s
Description: S/MIME Cryptographic Signature
