I'm indetermined. Using JSON exclusively instead of form encoded
parameters would give us the possibility to use structured parameters
(in and outbound) instead of a flat parameter list, which I would like
very much. But there are propably use cases where form encoded
parameters are better suited.
regards,
Torsten.
Am 21.04.2010 02:04, schrieb Manger, James H:
+1 to JSON as the one and only response format.
It is common enough. It is simple enough. It is flexible enough. It is
unambiguously specified enough.
I suggested a structure in the “application/credentials” thread.
http://www.ietf.org/mail-archive/web/oauth/current/msg01920.html
--
James Manger
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
