[MPlayer-users] Restarting mplayer after Network Trouble

[Reimar Döffinger]

On Sat, Mar 12, 2016 at 04:22:25AM +0100, Rasz wrote:
>  Problems start when trying to pause video. mplayer has no mechanism
> for that and will simply reply with [TCP ZeroWindow] signalling full
> buffer. Google web server will probe client(mplayer) with keep-alive
> packets for 300 seconds, after which it aborts concluding host
> crash/problems. Any attempts to continue playing after 300 seconds
> result in RST packet from google file server. Receiving RST makes
> mplayer choke for a second and close with no attempt at restarting.

Are you really using a current version?
That is exactly what the MAX_RECONNECT_RETRIES thing was
introduced for in 2012.

> Seeking in the video abandons current connection abruptly _without
> properly closing it_ and just starts another one.

Huh? What made you conclude that? MPlayer calls closesocket on the
old connection before opening the new one.

> At the very least there should be a way of making mplayer restart
> failed connection couple of times.

There is, by default, 5 times.

> Pausing should result in properly closed connection (maybe after a
> decent timeout), unpause should start new one.

I don't exactly see the point.
A lot of servers might be perfectly happy with keeping
the connection open as long as it takes, why should
the client add an arbitrary timeout?