>Consider a 2-minute delay to be a complete failure, because it is.
>Anything more than a few seconds is not useful. One reasonable (?)
>hack would be to limit that delay to not more than double the
>longest recorded round trip. Another would be a simple 2-second
>upper bound. Obviously these ideas are gross and broken, just
>like the Internet itself. Think "less broken", because a 2-minute
>delay is already more broken than I care to contemplate. Could you
>imagine using an editor with 2-minute delays? Spend a day hacking
>the kernel with an artificial 2-minute delay added. Ouch.
When you have an Internet connection that dumps you after 5 hours, you'll
think otherwise. As soon as I get dumped, I have it set to redial back the
University. Once the PPP is restablished, all of my connections are still
there. If I haven't typed anything on them since I was cut off, they have
no delay getting back. If I did type something, there's up to a 2 minute
delay (though typically only a few seconds) to get my connection working
again. If I don't get the same IP address (90% of the time I get the same
one), then obviously my connections don't work but it is _very_ handy to
not be disconnected. So here, a limit would only hurt things. It takes
~40-50 seconds to reestablish the PPP connection.
Windows immediately cuts me off from everything when that happens. Linux
will happily resume a three hour FTP transfer after I've long fallen
asleep.
-George
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html