Comment 5 for bug 790216

Well, at the very least then, it should remember the playhead position, so that you could resume by just hitting play. Right now, you can't heven know at which point it stopped (unless you were looking at the time counter just before it disappeared). That _is_ a pretty big deal.

> When the server or the network is overloaded, the *last* thing to do is immediately retry.

Well it could retry after a given (and settable) time interval and for a maximum given (and settable) number of times.

> Web browsers, email agent, newsgroups agents, aggregators... don't reconnect automatically either

FTP clients and download managers do, however.
Web browsers and email clients are programs that require continous user interaction (i.e. browsing) anyway, so it's ok if you occasionally need one more click in the case of a failure. A stream is something you usually leave playing while you are not in front of the computer with your hand on the mouse and keyboard, just like an FTP client or a download manager is something you usually leave downloading while you are away, More robustness is required in these cases, of course without unreasonably flooding the network with requests.

Anyway, these random stops happen so often that I wonder whether these are real network/server failures or if there's something wrong on the client side. May you suggest a way to dump (relevant) network traffic so that I could dig into the issue?

thanks
m.