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

Re: RfC: Is Web Sockets API ready for LC publication? [Was: Re: [websockets] Getting WebSockets API to Last Call]

From: Arthur Barstow <art.barstow@nokia.com>
Date: Tue, 20 Sep 2011 06:56:10 -0400
Message-ID: <4E78714A.4020601@nokia.com>
To: ext Brian Raymor <Brian.Raymor@microsoft.com>, Ian Hickson <ian@hixie.ch>, public-webapps <public-webapps@w3.org>, Jonas Sicking <sicking@mozilla.com>
Yesterday, Hixie checked in a fix for 13777.

Bug 13104 (Enable keepalive on WebSocket API) was closed (WontFix) but 
reopened on September 18. Since various group members agree with not 
addressing this bug for v1, I will proceed with a CfC to publish a LC of 
the Web Socket API. (Perhaps this bug could be moved to the PostPoned 
state and (re-)considered for v2?).

Editorial bugs 12510 and 13700 will not block the LC (although it would 
be great if they were fixed ;-)).

If any new bugs are submitted after the RfC begins, we will consider 
those bugs as LC comments.


On 9/15/11 9:07 AM, Arthur Barstow wrote:
> As an update on this RfC, note that ATM, 13777 is the only 
> non-editorial bug that remains open:
> <http://www.w3.org/Bugs/Public/show_bug.cgi?id=13777>
> I would appreciate it, if people would please provide input on this bug.
> -AB
>> On 9/9/11 6:05 PM, ext Brian Raymor wrote:
>>>   13777 - The WebSocket protocol draft (hybi-10) restricts the value 
>>> of subprotocols as follows: The elements that comprise this value 
>>> MUST be non- empty strings with characters in the range U+0021 to 
>>> U+007E not including separator characters as defined
>>> New, Assigned to Ian Hickson
>>> MICROSOFT PROPOSAL: We'd like to see the spec updated as outlined in 
>>> this bug.
Received on Tuesday, 20 September 2011 10:56:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:23 UTC