Could you add something to detect hanged (unresponsive) downloads, so that timeouts can be detected after a large part of a file has already been downloaded, and the connection freed to get another download slot to resume the download from another host ?

This case occurs when a remote agent disconnects abruptly from the network, without explicitly closing the session that had an upload in progress. The downloading LimeWire agent does not seem to detect timeouts (even after waiting for hours).

The other case occurs when a single agent shares many files that were found with the same search (for example many resources about the same author, artist, or genre): we can select a collection of files, expecting that the remote agent will accept one or more connections, and queuing others. However, there are some agents that accept any number of remote connections, start uploading them, then suspend them indefinitely while performing other uploads to our same LimeWire agent. So these files remain in a stale status (even when the last accepted upload terminates).

For now, we can just abort the download, but the uncomplete file remains in the temp folder, and there does not seem to have another search starting to find another responsive host to resume the download, and we must restart downloading the file completely...