Open fancycode opened 6 years ago
Hmm the chat backend is not settled yet as far as I understood.
From my POV we basically listen to the event for new chat/system messages, add a "pull for messages please" message to the signaling and remove the chat polling. The problem I see with this is that the ping was replaced with the chat polling, so this needs to be replaced/kept in mind too.
The standalone signaling server "pings" connected clients internally, so this shouldn't be a problem.
Just noticed this happening and was wondering why we still poll.
I didn't see any signaling events for message sending, so I guess it's not implemented yet in the signaling server ?
It's not implemented in the signaling backend in talks php. But also it's something for later
But also it's something for later
Is this still valid? What blocks this?
Allocating time on all clients. It's still favored for the future, but nothing short term, but it was discussed recently again as potential improvement for scaling.
The chat currently polls for new messages. When using the standalone signaling server, this should be changed to be event based to reduce the server/database load and improve latency.