On Wed, Apr 28, 2010 at 5:25 PM, Joseph Smarr <[email protected]> wrote: > > Any reason that wouldn't work?
Form encoding allows duplicate keys. So, transforming such message bodies to JSON should be defined. But, really, I think the group should just pick one and avoid the hassle. I would pick JSON, since JSON implementations bring reasonable Unicode conformance. -- Robert Sayre "I would have written a shorter letter, but I did not have the time." _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
