It's similar to running netcat in server mode, wrapping a script. It's even closer to doing that using websocat [1], whereby one does not have to do the websock

It's similar to running netcat in server mode, wrapping a script. It's even closer to doing that using websocat [1], whereby one does not have to do the websocket header juggling. The main difference is that while netcat or websocat will spawn a new process for each connecting client, ScaleSocket has a concept of rooms (channels). For a room, a process is spawned once only. All clients connecting to the same room are routed to the same process. This is not straight forward to do using the forementioned tools. There's a small comparison page [2] where I have mentioned some alternative tools. [1] https://github.com/vi/websocat https://github.com/vi/websocat [2] https://www.scalesocket.org/man/comparison https://www.scalesocket.org/man/comparison