title: Websocket onclose/onerror events does not fire if server crashes
body: <p>I have observed the following behavior in Firefox 4 and Chrome 7:</p>
  
  <p>If the server running the websocket daemon crashes, reboots, loses network connectivity, etc then the 'onclose' or 'onerror' events are not fired on the client-side. I would expect one of those events to be fired when the connection is broken for any reason.</p>
  
  <p>If however the daemon is shutdown cleanly first, then the 'onclose' event is fired (as expected).</p>
  
  <p>Why do the clients perceive the websocket connection as open when the daemon is not shutdown properly?</p>
  
  <p>I want to rely on the expected behavior to inform the user that the server has become unavailable or that the client's internet connection has suffered a disruption.</p>