If other customers want to get a download of a file, they will request the file and reopen every 10-20 minutes to confirm that it is still a valid source. However, some clients may adjust to make requests more frequent. These modified clients may have more opportunities to get an upload channel on the Donkey Client (edonkey). EMule (Mule) will not consider the frequency of the request and gain access to the upload channel will not increase. This behavior can be a huge waste of valuable resources (connectivity and bandwidth), so clients with this behavior are blocked.
The new client system will blacklist those clients that are frequently requested (more than one request in 10 minutes) and will not be able to get a download. The blacklist will be emptied after the emule is restarted.
Some examples of blacklisted (will not be available for download from the emule client):
> Set the client request parameter to less than 10 minutes.
> Pause downloads and quickly recover to speed up download-the effect is equivalent to sending a new download file request (only the Donkey client (edonkey)).
> Restart the client every 2 minutes (equivalent to sending a new request).
EMule does not care what kind of client (EMule)/edonkey (electric Mule)/mldonkey/shareaza) at the request. Any client that is frequently requested will be blocked.