W3C home > Mailing lists > Public > public-webapi@w3.org > October 2006

XMLHttpRequest: Why list HTTP method names

From: Subbu Allamaraju <subbu.allamaraju@gmail.com>
Date: Mon, 9 Oct 2006 16:52:50 -0600
Message-ID: <e3f21b1a0610091552r6872389asb248969512e853dd@mail.gmail.com>
To: "Web APIs WG (public)" <public-webapi@w3.org>
I find a bit odd for the XMLHttpRequest draft to require all implementations
to support the listed method names. In particular, what the motivation for
the conformance statement -

"User agents *must* at least support the following list of methods (see [
RFC2616 <http://www.w3.org/TR/XMLHttpRequest/#RFC2616>],
[RFC2518<http://www.w3.org/TR/XMLHttpRequest/#ref-rfc2518>],
[RFC3253 <http://www.w3.org/TR/XMLHttpRequest/#ref-rfc3253>],
[RFC3648<http://www.w3.org/TR/XMLHttpRequest/#ref-rfc3648>]
and [RFC3744 <http://www.w3.org/TR/XMLHttpRequest/#ref-rfc3744>])"
The method list should be an implementation choce. Moreover, the current
language does not allow special purpose implementations, say, to want to
support only GET and POST.

Subbu



-- 
------------------------------
http://www.subbu.org
Received on Monday, 9 October 2006 22:52:58 GMT

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