On 2010-04-30, at 9:02 AM, Yaron Goland wrote: > I actually have a preference for application/x-www-form-urlencoded but it's > not overwhelming, the key thing I believe we need to do is have exactly one > request/response format. In other words, I don't believe we should use one > format for requests and another for responses. Just pick one for both.
Using JSON for both seems weird relative to existing implementations. Look at the Facebook Open Graph API. Given FB's presence, a pattern that will be widely adopted and understood. Parameters are on the query line, and results are in JSON. If we changed the response from the AS to JSON, it would seem natural to a FB developer. Now they have to decode responses to the AS as being application/x-www-form-urlencoded, and the other are JSON. -- Dick _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
