W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [XHR] responseType "json"

From: Henri Sivonen <hsivonen@iki.fi>
Date: Fri, 2 Dec 2011 18:03:37 +0200
Message-ID: <CAJQvAud8i36rc7C36=D76-TP3QQmwoBYERwV_3gOMj+X_RhQxg@mail.gmail.com>
To: WebApps WG <public-webapps@w3.org>
On Fri, Dec 2, 2011 at 3:41 PM, Robin Berjon <robin@berjon.com> wrote:
> On Dec 2, 2011, at 14:00 , Anne van Kesteren wrote:
>> I tied it to UTF-8 to further the fight on encoding proliferation and encourage developers to always use that encoding.
>
> That's a good fight, but I think this is the wrong battlefield. IIRC (valid) JSON can only be in UTF-8,16,32 (with BE/LE variants) and all of those are detectable rather easily. The only thing this limitation is likely to bring is pain when dealing with resources outside one's control.

Browsers don't support UTF-32. It has no use cases as an interchange
encoding beyond writing evil test cases. Defining it as a valid
encoding is reprehensible.

Does anyone actually transfer JSON as UTF-16?

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Friday, 2 December 2011 16:04:18 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:49 GMT