[niemand]

See attached photo: Why?

There was nothing wrong with the mirror that got 99,96% of the file, yes it lost the connection and resumed with a different file.

JD could have instead just

1: resumed the file that was almost done,not starting a different one from the same source, instead of starting it over from 0% from a different source (as I said, not trouble with the previous source, since it just started loading on another part).

2: realise that the file is almost done, keeping it on hold until the original source was free again from downloading the next part, and resuming

This is wasting so much time reloading stuff that is already there just because the connection got lost for a second.

[Jiaz]

This will be part of the nextgen download core that I'm working on. At the moment the resume information from Link X is not accessable by Link Y and therefore it cannot resume another Link/Host download.