Author: Scopique

Here's an example of using the web socket server to handle messages and store the results in Redis. Since I wrote this, modifications have been considered, but that's a post for another day.

Before we move to the next part of the WS + API Server series, I wanted to talk a bit about Redis and Redis-OM.

Now we're getting somewhere: dynamically handling messages from the client.

Our main entry point sets up our combined HTTP(S) and WS server, but attempting to communicate with the server using either protocol will result in no response. In this post, we’re going to look at the middleware that allows the server to…

Before we continue with code, I wanted to stop off and talk at a very high level about HTTP and WS, and what each protocol means to me from a purpose standpoint.

Ever server needs a starting point, although this one doesn't do much on its own.