Examples for websocket clients and servers
WebSockets are an extension to the HTTP specification that support full duplex, aka two-way, session-based communication between client and server. A standard HTTP exchange between client and server is initiated by a client request. The server, on receiving the request, sends back a response, then closes the connection between the two. The server can’t initiate an exchange, and communication can’t go both directions at once. WebSockets expand on HTTP by allowing for both of these features.
A WebSocket connection works as follows: the client request via HTTP or HTTPS. The server responds with an upgrade message and sends a key for encryption. The client responds, the server opens an encrypted socket between the two. Either side can send a message at any time, and either side can close the connection. The protocol supports a message event, for when a new message arrives. and a close event, for when the remote host closes the connection.
WebSockets bear some resemblance to MQTT, a message-based protocol for communication between low-power networked devices. Here is a comparison between the two.
These clients can be used with the ExpressWsServer as well as on their own, connecting to a different server (see Testing Servers, below). A version of the jsClient is included in the ExpressWsServer directory.
To test a WebSocket client, you need a WebSocket server. If you don’t want to write your own, here are two options:
Postman is a tool for testing various web protocols. It allows you to send all kinds of HTTP, WebSocket, RPC, etc. requests to test the responses a server would give. You can either make an account and use their browser interface or download their desktop client. Their WebSocket echo server supports both the raw WebSocket protocol and some of the additions from the socket.io JavaScript library. It’s a useful echo server to test clients on.
Websocketd is a command line application, available for MacOS, Windows, and
Linux, which creates a WebSocket server and connects it to another command line application. To make it work, you need to have a command line script or program which will listen and respond. The websocketd examples show how to write a simple command line script to respond. You could write something more complex in node.js, python, etc. or you could use the command line program tee to echo the response back to the client and save to a local file, like so:
$ websocketd --port=8080 tee log.txt
Both the Postman WebSocket echo server and the websocketd echo server will only send messages back to the client that sends them. Neither will not broadcast to other clients. For a server that will broadcast to all clients, you’ll need to write your own. There are a couple of node.js examples below.
These examples the server-side WebSocket library, ws.
To get the servers below working, you’ll need node.js installed. Once you have that, download the repository, then, on the command line, change directories into the directory of each server example. Once you’re there, install the libraries using npm, the node package manager, like so:
$ npm install
This will download the necessary libraries. Then run the server like so:
node server.js
The server ExpressWsServer is an HTTP server that also support WebSockets. When you’re running it, open a browser and enter http://localhost:3000/ in the address bar. The server script will serve you the index.html page in the public folder, which is a browser-based client of the server. You can also load the jsClient example by opening the index.html page from that example in a browser. It will connect to the server running on your terminal window as well.
To stop any node.js script, type control-C in the terminal window.
The WsServerExample does not have a HTTP server included in it, it is just a WebSocket server. You can run it the same way as the others, but only the Arduino example of an HTML file opened from the local filesystem can connect to it. The server will not serve an HTML page itself.