- From: <bugzilla@jessica.w3.org>
- Date: Sat, 06 Aug 2011 00:13:39 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13295 Brian Raymor [MSFT] <brian.raymor@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NEEDSINFO | --- Comment #2 from Brian Raymor [MSFT] <brian.raymor@microsoft.com> 2011-08-06 00:13:38 UTC --- If the connection is not established, then the preference is to treat this as a "user cancel" rather than an error and simply "close the websocket connection" and fire onClose. The other option is to be specific about the "fail the websocket connection" behavior for this case and indicate onError is not fired. Based on the definition of "fail the websocket connection" in the protocol draft, "report the problem to the user" is a MAY: http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-10#section-7.1.7 Certain algorithms and specifications require an endpoint to _Fail the WebSocket Connection_. To do so, the client MUST _Close the WebSocket Connection_, and MAY report the problem to the user (which would be especially useful for developers) in an appropriate manner. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Saturday, 6 August 2011 00:13:40 UTC