W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 29 Jul 2011 16:50:22 +0000 (UTC)
To: Takeshi Yoshino <tyoshino@google.com>
cc: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.64.1107291648190.18680@ps20323.dreamhostps.com>
On Fri, 29 Jul 2011, Takeshi Yoshino wrote:
> 
> While conducting such experiments, user-agents are not standard 
> compliant. If W3C/WHATWG are confident that violating specs is the right 
> way to evolve specs, I'll stop arguing this. Yes, we'll make our 
> browsers standard non-compliant to seek the way to improve WebSocket.

I can't speak for the W3C, but yes, extensions to the standards are how we 
evolve the technology stack. As extensions are developed and adopted by 
browsers, the API spec will be updated accordingly. Updating the spec is a 
trivial matter.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 29 July 2011 16:50:46 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:46 GMT