On Tue, Jan 13, 2009 at 2:19 PM, Henning Schmiedehausen < [email protected]> wrote: > > I was wondering on how to deal with this, mainly because the > corresponding javascript code in core.io/io.js also has no concept of > the other side failing (even the spec at > > http://www.opensocial.org/Technical-Resources/opensocial-spec-v08/gadgets-reference08#gadgets.io.makeRequest > is pretty much ignoring the fact that the other side could fail. What > would be the preferred response. Do as if nothing happened and just > return an empty json object?) >
Empty json would be bad. A json object with an "rc" attribute of 503 and the body of the HTTP response would be better. I've just finished a bunch of changes in OAuthRequest to do better error reporting for OAuth issues, but for the most part the goal was to proxy the response from the origin server right back to the application.
