W3C home > Mailing lists > Public > public-html@w3.org > December 2007

Re: [XHR] send doesn’t explain what to do when method is GET

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 17 Dec 2007 16:38:24 -0800
Message-ID: <47671680.7060301@sicking.cc>
To: Julian Reschke <julian.reschke@gmx.de>, "public-html@w3.org" <public-html@w3.org>

Julian Reschke wrote:
> Jonas Sicking wrote:
>>> No.  Look, if you don't want to have to take on the extra work of
>>> fully supporting HTTP (for what is, admittedly, currently a fringe
>>> case), fine, don't.  Just please don't ask that we tell those who are
>>> willing to do so, that they can't.
>> Given that none of the current browsers support this today, I'm not 
>> sure who we would help by saying that this is non-conformant behavior.
> The suggestion was *not* to say anything about it, and just to rely on 
> the normative spec for it, which is RFC2616 now and will be RFC2616bis 
> in the future.

But not saying anything is likely to hurt compatibility between 
implementations and make authors rely on features that only work in some 

/ Jonas
Received on Tuesday, 18 December 2007 00:37:58 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:29 UTC