Stealth: WS Connection Refactor about stealth HOT 2 CLOSED

The WebSocket Connection state handling needs to be transparent. The major difference from all other network protocols (so far) is the ping/pong/close workflow that WS13 describes.

Currently, the parsing mechanism implements a response property that influences the connection state. This should be decoupled, so that the new WS Packet Parser can be used to analyze a packet before it's being processed - and be integrateable once the WS protocol is being used as an alternative tunneling protocol.

Nevertheless the ondata() callback should be used as a place to do this kind of handling, as the WS.receive() method isn't the right place for it as it can be called by outside mechanisms that are independent of the connection (aka connection being null).

from stealth.

This has been implemented, reviews have been fixed and is up and running as the new binary-embracing protocol.

At a later point in time, there might be support for the gzip frame-by-frame compression that Chromium uses by default (and is limited to ~131kB frame size)

from stealth.