Hello everyone,
A little hope this time: we came up with a fix for data pipelining,
but it affects backward compatibility for server-to-server RPCs a
little bit. If you're sending requests from your server to
/social/rpc, you must be ready to accept a JSON response that contains
a "result" or a "data" field in the response. Orkut currently sends
only the "data" field, and the javascript code that you are running
right now only looks for the "result" field. Orkut will start sending
both now. It shouldn't hurt anyone if their code was already written
to expect either of the fields set. It could break clients that expect
the "data" field to be the first or the only field in the response.
To see the main discussion, check out the JIRA issue:
https://issues.apache.org/jira/browse/SHINDIG-1144
I'll push sandbox with this change today and include it in the next
orkut push. Once sandbox is pushed and we see no further issues, I'll
give you a final date for the fix to reach production.
Again, let me reiterate that gadgets calling ViewerRequest or
OwnerRequest don't need to be changed. Only look at your server-side
code if your server calls opensocial RPCs directly on Orkut.
Regards,
Tiago