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

Re: RfC: LCWD of WebSocket API; deadline August 30

From: Takeshi Yoshino <tyoshino@google.com>
Date: Fri, 10 Aug 2012 13:34:53 +0900
Message-ID: <CAH9hSJYaT2=ts_dXLZdS_T8PWmkug3an7WT8RF44YQHRBD3rfQ@mail.gmail.com>
To: Arthur Barstow <art.barstow@nokia.com>
Cc: public-webapps <public-webapps@w3.org>
No technical comments.

A few editorial comments.

> CLOSING (numeric value 2)
> The connection is going through the closing handshake.

The readyState can enter CLOSING also when close() is called before
establishment. In that case, it's not going through closing handshake.

>  // networking
>           attribute EventHandleronopen;

insert an SP between EventHandler and onopen
(already fixed on the editor's draft)

> When the user agent validates the server's response during the "establish
a WebSocket connection" algorithm, if the status code received from the
server is not 101 (e.g. it is a redirect), the user agent must fail the
websocket connection.

websocket -> WebSocket

> If the user agent was required to fail the websocket connection or the
WebSocket connection is closed with prejudice, fire a simple event named
error at the WebSocket object. [WSP]

websocket -> WebSocket

> interface CloseEvent : Event {
>   readonly attribute boolean wasClean;
>   readonly attribute unsigned short code;
>   readonly attribute DOMString reason;
> };

missing anchor on reason to its description
Received on Friday, 10 August 2012 04:35:45 GMT

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