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

Re: UAs shipping unprefixed websocket API implementations?

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 02 Aug 2011 10:04:32 -0400
Message-ID: <4E3803F0.8050006@mit.edu>
To: Anne van Kesteren <annevk@opera.com>
CC: public-webapps@w3.org
On 8/2/11 9:55 AM, Anne van Kesteren wrote:
> On Tue, 02 Aug 2011 15:48:53 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> http://blog.chromium.org/2011/08/new-websocket-protocol-secure-and.html indicates
>> that the Chrome dev channel now has an unprefixed implementation of
>> the WebSocket API, as far as I can tell. Also as far as I can tell,
>> the API is not really stabilized yet (e.g. there's the big open
>> question about whether the compression stuff is required or forbidden).
> That was resolved.

What was the resolution?  I missed this, apparently....

> Note that Chrome was already shipping an unprefixed
> API to date, just with an older version of the protocol.

:(  That really sucks, because it makes it that much harder for 
implementations to ship updated unprefixed versions.  :(

Can we please try to avoid shipping unprefixed versions of unstable 
specs?  Please?

Received on Tuesday, 2 August 2011 14:05:00 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:34 UTC