ws: a node.js websocket library
ws
is a simple to use WebSocket implementation, up-to-date against RFC-6455,
and probably the fastest WebSocket library for node.js.
Passes the quite extensive Autobahn test suite. See http://websockets.github.com/ws for the full reports.
Protocol support
- Hixie draft 76 (Old and deprecated, but still in use by Safari and Opera.
Added to ws version 0.4.2, but server only. Can be disabled by setting the
disableHixie
option to true.) - HyBi drafts 07-12 (Use the option
protocolVersion: 8
) - HyBi drafts 13-17 (Current default, alternatively option
protocolVersion: 13
)
Installing
npm install --save ws
Opt-in for performance
There are 2 optional modules that can be installed along side with the ws
module. These modules are binary addons which improve certain operations, but as
they are binary addons they require compilation which can fail if no c++
compiler is installed on the host system.
npm install --save bufferutil
: Improves internal buffer operations which allows for faster processing of masked WebSocket frames and general buffer operations.npm install --save utf-8-validate
: The specification requires validation of invalid UTF-8 chars, some of these validations could not be done in JavaScript hence the need for a binary addon. In most cases you will already be validating the input that you receive for security purposes leading to double validation. But if you want to be 100% spec conform and fast validation of UTF-8 then this module is a must.
Sending and receiving text data
var WebSocket = ;var ws = 'ws://www.host.com/path'; ws; ws;
Sending binary data
var WebSocket = ;var ws = 'ws://www.host.com/path'; ws;
Setting mask
, as done for the send options above, will cause the data to be
masked according to the WebSocket protocol. The same option applies for text
data.
Server example
var WebSocketServer = Server wss = port: 8080 ; wss;
ExpressJS example
var server = url = WebSocketServer = Server wss = server: server express = app = port = 4080; app; wss; server;server;
Server sending broadcast data
var WebSocketServer = Server wss = port: 8080 ; wss { wssclients;};
Error handling best practices
// If the WebSocket is closed before the following send is attemptedws; // Errors (both immediate and async write errors) can be detected in an optional// callback. The callback is also the only way of being notified that data has// actually been sent.ws; // Immediate errors can also be handled with try/catch-blocks, but **note** that// since sends are inherently asynchronous, socket write failures will *not* be// captured when this technique is used.try ws; catch e /* handle error */
echo.websocket.org demo
var WebSocket = ;var ws = 'ws://echo.websocket.org/' protocolVersion: 8 origin: 'http://websocket.org'; ws; ws; ws;
Other examples
For a full example with a browser client communicating with a ws server, see the examples folder.
Note that the usage together with Express 3.0 is quite different from Express 2.x. The difference is expressed in the two different serverstats-examples.
Otherwise, see the test cases.
Running the tests
make test
API Docs
See /doc/ws.md
for Node.js-like docs for the ws classes.
Changelog
We're using the GitHub releases
for changelog entries.
License
(The MIT License)
Copyright (c) 2011 Einar Otto Stangvik <einaros@gmail.com>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.