Okay... a few things are being conflated here... A websocket connection is a stream connection to a server... that's it.
From there, you can use different queuing patterns for relaying messages to other connected users, but that process will widely vary. While this does discuss the different patterns for communication, there's several missing and others that are not spelled out that well.
While Off-topic better examples can be found in the 0mq introduction and documentation, or for that matter RabbitMQ. Lately I've found that most of these patters are better implemented behind Redis with filters against connected sockets for relay managed by the application if needed.
YMMV.
tracker1 1196 days ago. link 1 point ▲ ▼