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

Re: XMLHttpRequest: Why list HTTP method names

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 13 Oct 2006 02:16:25 +0200
To: "Subbu Allamaraju" <subbu.allamaraju@gmail.com>, "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <op.thb21ncl64w2qv@id-c0020.wanadoo.nl>

On Thu, 12 Oct 2006 15:13:31 +0200, Subbu Allamaraju  
<subbu.allamaraju@gmail.com> wrote:
> a. Method support - this is dictated by the programming model exposed to  
> the component developer. This model currently does not map for methods  
> other
> than GET and POST.

This has been changed. Now must support GET, POST, HEAD, PUT and DELETE  
and you must unless you have a very good reason not to support all others  
as well except for those which have security concerns attached to them.


> b. Semantics on field access - in particular the need to throw
> INVALID_STATE_ERR (will start a new thread on that)

See that thread.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Friday, 13 October 2006 00:16:37 GMT

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