3 ms·
I don't see how anything would be much more robust than HTTP. Any network based protocol can fail at any time, so you're going to have to have some concept of t
by anderspitman 6y ago
I don't see how anything would be much more robust than HTTP. Any network based protocol can fail at any time, so you're going to have to have some concept of tracking your progress and retrying failed requests. Both are easy to do with HTTP. Can you give a concrete example of something that would work better than HTTP?
- parliament32 6y agoHere's an exercise for you: In your browser, start downloading a test file, like [1]. Turn off your network card for a few seconds, then turn it back on. See what your browser does. Next, start downloading a large file over Bittorrent, like [2]. Turn off your network card for a few seconds, then turn it back on. See what the client does. [1] http://speedtest.tele2.net/100GB.zip http://speedtest.tele2.net/100GB.zip [2] https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-10.5.0-amd64-DVD-1.iso.torrent https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/de...
- anderspitman 6y agoThis has nothing to do with HTTP. It's just poor behavior on the part of the browser.