It's currently a bit hard to add new features to the websockets
If the websockets are not deployed, we can't send messages between clients
It's one more codebase to maintain and evolve
Needs
The idea is to use cloudAMQP (available on Heroku) and to use it to maje AMQP over websockets available (see this link for explanations and this link for a more complete example). Thus the need for a dedicated websocket server would not exist anymore as the API can only push messages in the AMQP cluster that are sent to the user directly. The interpretation of the messages and their meaning would then be done front-side, depending on the routing of the message.
Context
Needs
The idea is to use cloudAMQP (available on Heroku) and to use it to maje AMQP over websockets available (see this link for explanations and this link for a more complete example). Thus the need for a dedicated websocket server would not exist anymore as the API can only push messages in the AMQP cluster that are sent to the user directly. The interpretation of the messages and their meaning would then be done front-side, depending on the routing of the message.