Bug 15595 - The abstract could be improved by pointing out that "WebSocket protocol" is defined by the IETF, while this API specifies the browser API to use that protocol. "The send(data) method transmits data using the connection. If the readyState attribute is CONN
Summary: The abstract could be improved by pointing out that "WebSocket protocol" is d...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebSocket API (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: public-webapps-bugzilla
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-17 15:55 UTC by contributor
Modified: 2012-05-02 19:45 UTC (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description contributor 2012-01-17 15:55:40 UTC
Specification: http://dev.w3.org/html5/websockets/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
The abstract could be improved by pointing out that "WebSocket protocol" is
defined by the IETF, while this API specifies the browser API to use that
protocol.

"The send(data) method transmits data using the connection. If the readyState
attribute is CONNECTING, it must throw an InvalidStateError exception." - What
happens for the other non-OPEN states? 

"unpaired surrogates" is mentioned in three places, but not defined anywhere.
What is that? In the same context, "with prejudice" is mentioned multiple
times, only referencing the WebSockets protocol (instead of defining that),
but the protocol doesn't mention that term.

Posted from: 78.49.193.126
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7
Comment 1 Ian 'Hixie' Hickson 2012-05-02 19:45:25 UTC
> Comment:
> The abstract could be improved by pointing out that "WebSocket protocol" is
> defined by the IETF, while this API specifies the browser API to use that
> protocol.

Done by adding a parenthetical regarding the source of the protocol. (When the abstract was written, the protocol was part of the same spec, IIRC.)


> "The send(data) method transmits data using the connection. If the readyState
> attribute is CONNECTING, it must throw an InvalidStateError exception." - What
> happens for the other non-OPEN states? 

The very next sentence in the spec answers that already.


> "unpaired surrogates" is mentioned in three places, but not defined anywhere.

I've changed this to not use a term of art but (it talks about surrogates that are isolated, now), and added a reference to [UNICODE].


> In the same context, "with prejudice" is mentioned multiple
> times, only referencing the WebSockets protocol (instead of defining that),
> but the protocol doesn't mention that term.

The term "with prejudice" is defined at the target of the cross-reference; it controls what events are fired in certain cases.