… this !== window
… include in previous commit)
The WebSocket.buffer would continue to grow, unabated, for each new message. This buffer is now only utilized to process the nonce, and is set to empty (and no longer filled) once nonce has been received. Parser instance appears to handle all message buffering, instead of WebSocket entity.
…er.options.log -> self.listener.options.log)
… WebSocket write error
…ly swallowed by any of the transports
…utoreconnect through a different socket. In this case we still want to clear the FD but not call onDisconnect immediately.
Destroy the fds on disconnect Restored 20 secs of polling so that node doesn't timeout the connections
Important fix for polling transports.
it will prevent the buffers from being flushed and will result in corrupted responses for the xhr-polling transport. According to the node documentation "destroy" is only necessary in case of a errors.