- From: <bugzilla@jessica.w3.org>
- Date: Fri, 05 Aug 2011 23:34:03 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13294
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |FIXED
--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-05 23:34:02 UTC ---
Failing the WebSocket connection involves sending more data. We can't send more
data in this situation, by definition (that's why we're giving up, after all).
But we can still fire an 'error' event, sure. Done.
Note that both 'error' and 'close' are fired asynchronously (well, they're
fired synchronously, but on a task that is queued after the connection is
closed).
--
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 Friday, 5 August 2011 23:34:04 UTC