This is a proposal to add websockets as a new module for Node.js.

This implementation attempts to adhere to RFC 6455. If differences are
identified I will supply the necessary changes. This implementation does
not attempt to parse connection header values, such as extensions or
sub-protocols values.

This proposal focuses exclusively on Node's APIs from its core modules
and then supplies additional options as necessary to populate callbacks
and RFC 6455 connection header values.

Some notes about performance.

Everybody that writes a websocket library wants to measure performance
in terms of message sent speed, which seems to be a red herring. Message
send speed is trivial compared to message receive speed.

Message send speed appears to be a memory bound operation. Using this
approach to websockets I send at about 180,000 messages per second on my
old desktop computer with slow DDR3 memory. On my newer laptop with
faster DDR4 memory I can send at about 460,000 - 480,000 messages per
second. This speed is largely irrelevant though because at around
460,000 messages garbage collection kicks in and message send speed
slows to a crawl at around 5,000 per second.

Message receive speed is much slower and far more dependent upon the
speed of the CPU. On my old desktop I can receive messages at a speed of
around 18,000 messages per second while on my laptop its a bit slower at
around 12,000-15,000 messages per second because the desktop has a more
powerful CPU. The speed penalty on message reception appears to be due
to analysis for message fragmentation. This approach accounts for 4
types of message fragmentation.

…tion.

…ageHandler