When a fast donload catches up to the border of another previously (or currently) downloaded segment of a file, Xolox should throw away that segment and continue with the fast download.

That way you keep the precious fast connection. This is a good idea if the segment to throw out is small in comparrison to the entire file, or if it is small in comparrison to the donload speed.


This feature would prevent this anoying behaviour: You are downloading a file using two connections, one at 50k/s, the other at 3. After one hour you have 53% of the file downloaded, and xolox drops the fast connection. You are stuck with a slow connection that would require days to download the file, while the fast connection would have whizzed past the small 3% segment in a few minutes.

XoloX does drop the faster connection when it catches up with the next segment, but will try to reconnect immediately (in this case, where there are not queued hosts) to start another segment.