Quote:
Originally posted by stief
Hmmm. Tooltip's observation that "the 97 KB are transferred in fractions of seconds, but the request for the next 97 KB chunk takes some seconds" seemed to match the connection problems I'd noticed in java clients. Making chunksize dependent on connection quality sounds good (this isn't "handshaking?"). |
Of course it might slow the download down a little bit if the http headers have to be parsed again but that doesn't even take one second. I suspect the period of time a download remains in a 'Connecting...' state depends more on the refresh rate of the GUI.
Quote:
| Might hosts drop the TCP connections if the HTTP was unexpectedly slow or the user killed it, and can't I trigger a TCP reconnect? |
LimeWire does not retry hosts if the TCP connection failed because it assumes that a remote host won't drop a TCP connection without a reason. Kill/Resume will cause LimeWire to retry a failed connection but you will loose all your alternate locations.