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

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

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 15 Dec 2007 11:45:23 +0100
Message-ID: <4763B043.3060905@gmx.de>
To: Jonas Sicking <jonas@sicking.cc>
CC: Mark Baker <distobj@acm.org>, Stewart Brodie <stewart.brodie@antplc.com>, public-webapi@w3.org

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.

BR, Julian
Received on Saturday, 15 December 2007 10:45:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:59 GMT