Or even when changing networks (LTE->wifi or wifi->LTE), this would make it easier to re-establish the connection than quitting the application and reopening it. This would, I think, allow better websockets management and avoid connections being open for hours. Why not set up a number of reconnection attempts?įor example, the client tries to reconnect 3 times, and if none of the attempts work, the connection is aborted. Having the client send a message and the server reply every X seconds/minutes would eliminate the problem and prevent the connection from staying open for 1 hour for no reason, as in the nginx configuration.Īlso, I saw a message saying that if a connection was closed unexpectedly, for resource reasons, there was no attempt to reconnect. Or if, when playing an episode of a series lasting 40 minutes, the viewer pauses the video for 20 minutes, the connection will be closed before the end of the episode. In the case of haproxy or nginx, if someone pauses a video that lasts more than an hour (a movie, for example), the websocket timeout will occur before the end of the movie. Apart from reverse proxies such as caddy or traefik (for those I know) there is no real timeout for websockets.įor reverse proxies like haproxy or nginx, the timeout is defined either by default or by the user. Is it possible that in a version of emby a "ping pong" is performed in websocket to maintain a connection via a reverse proxy?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |