> Web browsers, email agent, newsgroups agents, aggregators. Well it could retry after a given (and settable) time interval and for a maximum given (and settable) number of times. > When the server or the network is overloaded, the *last* thing to do is immediately retry. Right now, you can't heven know at which point it stopped (unless you were looking at the time counter just before it disappeared). Well, at the very least then, it should remember the playhead position, so that you could resume by just hitting play. InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) Playback should ALWAYS resume when possible. Any temporary network issue should cause only temporary stream interruption, never a stop without a resume. If you can manually resume the playback (which is ALWAYS the case, by manually hitting play again and manually seeking the point where playbak has stopped), then the player should do all this automatically.Ī stream is by definition something that should never stop playing until it is finished. The client MUST be 100% bulletproof to all kinds of error conditions, and if anything fails, it MUST retry and retry and resume normal playback as soon as possible. It doesn't matter whether it is the server actually closing the connection, or if the server stops responding, or if the network connection is failing or none of these. VideoLan only shows playback control and the window is resized) and the playhead goes back to the beginning and stops showing current time and total time.Įverything is as if you had hit the stop button. htm?cont= 7pPpPlussPYNFVv okgeeqqEEqualĪt random times (it may be after several minutes), the stream stops playing and closes. Write or paste the address of a network stream, for example mediapolis.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |