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

Re: XMLHttpRequest: Why list HTTP method names

From: Robin Berjon <robin.berjon@expway.fr>
Date: Thu, 12 Oct 2006 11:39:11 +0200
Message-Id: <0DFFA06D-2D61-4C51-AD9E-FC74ED361356@expway.fr>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
To: Subbu Allamaraju <subbu.allamaraju@gmail.com>

On Oct 11, 2006, at 21:54, Subbu Allamaraju wrote:
> Two sum up, there does not seem to be any reason other than some  
> intent of making implementations support a base set of methods. If  
> the WG feels strongly about this, instead of saying a MUST or  
> SHOULD, the spec could add a statement "encouraging"  
> implementations support these base set of methods.

I'm sorry but I don't understand your use case at all. Furthermore, I  
don't see how you propose that we produce a specification that  
fosters interoperability by loosening the requirements on its most  
fundamental functionality. My personal opinion on the current draft  
is that we don't mandate enough methods, certainly not that we  
mandate too many.

-- 
Robin Berjon
    Senior Research Scientist
    Expway, http://expway.com/
Received on Thursday, 12 October 2006 09:39:28 GMT

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