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: Wed, 27 Jul 2011 22:52:04 +0000 (UTC)
To: Ian Fette (イアンフェッティ) <ifette@google.com>
cc: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.64.1107272251250.3775@ps20323.dreamhostps.com>
On Wed, 27 Jul 2011, Ian Fette (~B~B~C~C~U~B~C~C~C~F~B) wrote:
>
> I agree we shouldn't require deflate-stream it in the API. I don't agree 
> the API should specify an exact set of extensions, as that would prevent 
> any future versions/developments. A minimum baseline would be reasonable 
> though, once we have that minimum baseline in place (e.g. a stable set 
> of extensions that are well tested, such as compression and 
> multiplexing). I don't think we should put the cart before the horse.

As soon as there's a feature that browsers are to implement, we would 
update the WebSockets spec to list it as a requirement.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 27 July 2011 22:52:28 GMT

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