[Bug 13295] The "make disappear a WebSocket object" case should not fail the WebSocket connection
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13295 Ian 'Hixie' Hickson changed: What|Removed |Added Status|NEW |RESOLVED CC||i...@hixie.ch Resolution||NEEDSINFO --- Comment #1 from Ian 'Hixie' Hickson 2011-08-05 23:05:42 UTC --- I don't understand the question. What would you do instead? Let the handshake complete then close it? How would it be captured as an error condition? It's not like any events are going to be fired, the event queue is about to be torn down... -- 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.
[Bug 13295] The "make disappear a WebSocket object" case should not fail the WebSocket connection
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13295 Brian Raymor [MSFT] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NEEDSINFO | --- Comment #2 from Brian Raymor [MSFT] 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.
[Bug 13295] The "make disappear a WebSocket object" case should not fail the WebSocket connection
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13295 Ian 'Hixie' Hickson changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WONTFIX --- Comment #3 from Ian 'Hixie' Hickson 2011-08-08 21:24:49 UTC --- By the time you are to "make disappear a WebSocket object", no events are going to fire ever again for that WebSocket object â the entire event queue for the Document is about to be cleared. So the only difference here is at the protocol level, and even there, there is essentially no difference â in fact the only difference is that "fail" says that the UA "may" report a problem, as you quote. But then the UA is always allowed to do that. That's just UI. So anyway, I don't understand what difference this would ever make. I've left the spec as is. The requirements on user agents are identical. -- 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.
