quasi- Node.js net.Server, consumeable Websockify

[rektide]

Websockify is a fine websocket<->TCP proxy.

I'd like to also see this node.js port be useable within a Node.js process natively, without having to connect to the TCP port exposed by Websockify. Instead of creating a node.js process that listens for TCP, then having a separate websockify process that connects to it, Websockify could export a Node.js net.Server like object that emits connection events with something that works more or less like a net.Socket. By making Websockify embeddable inside Node programs, we skip having to make the in-between TCP connnection and host TCP services directly behind Websockify.

[kanaka]

That sounds like a great refactor. The python code is already split somewhat like that (websocket.py and websocketproxy.py).

I look forward to a pull request :-)