Discussion: Why does signalhub works on HTTP and not WS
Closed this issue · 1 comments
Hey,
I was wondering as this is a "signaling server" why it uses http and not websockets?
FTR I made a signalhub implementation based on websockets (here). I made this because we had issues where the browser (Chrome/FF) was requesting too many HTTP requests on top of our own and was slowing down the navigation.
IMO http with event sourcing is a good alternative to websocket, to improve this I think that the issue really resides in the way that the mesh calls broadcast
too much. Maybe that there's a better way to implement signaling by using more SSE to broadcast only when needed and therefore reduce the number of broadcast
calls. Anyway, closing this issue as I know believe that this solution is as strong as the one using websocket and that HTTP > WSS.