If true, fragmented messages will be automatically assembled and the full
message will be emitted via a message event. If false, each frame will be
emitted on the connection object via a frame event and the application
will be responsible for aggregating multiple fragmented frames. Single-frame
messages will emit a message event in addition to the frame event.
The number of milliseconds to wait after sending a close frame for an
acknowledgement to come back before giving up and just closing the socket.
Whether or not to fragment outgoing messages. If true, messages will be
automatically fragmented into chunks of up to fragmentationThreshold bytes.
The maximum size of a frame in bytes before it is automatically fragmented.
The maximum allowed received frame size in bytes. Single frame messages will also be limited to this maximum.
The maximum allowed aggregate message size (for fragmented messages) in bytes.
Which version of the WebSocket protocol to use when making the connection. Currently supported values are 8 and 13. This option will be removed once the protocol is finalized by the IETF It is only available to ease the transition through the intermediate draft protocol versions. The only thing this affects the name of the Origin header.