Site-wide WebSocket implementation

Open jeda opened this issue 5 years ago • 1 comments

This would help to have state correctly synced (whenver users are in rooms or not), properly update profiles in case of a refresh across all clients.

Taken a bit from crybapp/web#6.

Feb 11 '20 06:02 jeda

Personally, I think API should actually be split into a couple more microservices. having a single persistent websocket means we're tracking more sessions than necessary. We also should look into solidifying the service boundaries and tracking down what data comes from where and when.

Feb 11 '20 13:02 Soliel