[
https://issues.apache.org/jira/browse/SHINDIG-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739575#action_12739575
]
Adam Winer commented on SHINDIG-1144:
-------------------------------------
Note: simply swapping "result" for "data" will have bad backwards
compatibility repercussions:
- Existing clients talking to Shindig-based servers using JSON-RPC to retrieve
content will break
- Cached Javascript expecting "data" will break (or Javascript downloaded
during a rollout)
So, we need to be very careful in how we fix this. It may be necessary to use
two endpoints - a legacy endpoint with "data", a new endpoint with "result",
and eventually disable the legacy endpoint.
(BTW, the JSON RPC spec is relevant, but not the important spec here: that's
http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/RPC-Protocol.html
which also uses "result").
> JSON response uses the key "data" instead of "result ", in violation of the
> spec
> --------------------------------------------------------------------------------
>
> Key: SHINDIG-1144
> URL: https://issues.apache.org/jira/browse/SHINDIG-1144
> Project: Shindig
> Issue Type: Bug
> Reporter: Kartick Vaddadi
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> According to the JSON-RPC over HTTP spec at
> http://groups.google.com/group/json-rpc/web/json-rpc-1-2-proposal?pli=1#response-procedure-return
> , a JSON-RPC response that did not return an error should use the key
> "result" in the returned JSON object rather than "data".
> The Orkut JSON-RPC service at orkut.com/social/rpc exhibits this bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
