[DatHebIkWeer]

I understand that eMule bans users if it gets an upload request more than once every 10 minutes. I also understand that this is because once, long ago, a then popular ed2k client handled those requests in a wrong way so many requests would be advantageous to get a download quicker. I understand this was considered to clot up the network so it should be discouraged. But I also understand that eMule does not really get affected by those requests. The queuing system ensures that extra requests do not lead to faster downloads.

Considering that I would say in our days this ban for too many requests is folklore and a nice tradition, but may be past expiry.

Traditions are good and need to be honoured, but some traditions may hold us back. So does the ban system. In case of rare files for instance, if there is 1 source and only 1 requester, they may just sit there and stare at each other because they have to be careful not to get banned for requesting. Instead of using the available upload capacity they have to wait till they can start communicating. This is not right and might delay the system more than any other bad feature it may have.

Therefore I suggest we abolish the whole ban thing for this. We have developed and internet has developed. a simple queuing request more will not clot up connections anymore. And clients and mods that cannot handle a superfluous request properly should seriously consider their existence.

For the sake of it we can initially leave a fine system in place, for instance a request will cause your queue entry to be moved back a few places, but I guess even that won’t be really necessary.

Of course we should be protected against malicious code and viruses that do abundant requests with the purpose to bring the system down. But my guess is that that activity will lie more in the order of 100 requests per minute than in the order of 1 request per 10 minutes.

[tHeWiZaRdOfDoS]

DatHebIkWeer, on 07 July 2012 - 05:14 PM, said:

I understand that eMule bans users if it gets an upload request more than once every 10 minutes. I also understand that this is because once, long ago, a then popular ed2k client handled those requests in a wrong way so many requests would be advantageous to get a download quicker. I understand this was considered to clot up the network so it should be discouraged. But I also understand that eMule does not really get affected by those requests. The queuing system ensures that extra requests do not lead to faster downloads.

The reason is that this is BAD behaviour which puts additional, unnecessary load on the network - clients doing that SHOULD be punished. As you wrote: there's no advantage - so STOP DOING THAT and everyone's happy

Quote

Traditions are good and need to be honoured, but some traditions may hold us back. So does the ban system. In case of rare files for instance, if there is 1 source and only 1 requester, they may just sit there and stare at each other because they have to be careful not to get banned for requesting. Instead of using the available upload capacity they have to wait till they can start communicating. This is not right and might delay the system more than any other bad feature it may have.

They may have to wait a bit longer but it helps the network in the long run... though I agree that NNP sources should be asked more often or "call back" once they aren't NNP anymore.
Additionally, please remember that a client has to ask 4 times with timedifferences BELOW 10mins. before it gets banned! This isn't coincidence anymore but pure stupidity.

Quote

For the sake of it we can initially leave a fine system in place, for instance a request will cause your queue entry to be moved back a few places, but I guess even that won’t be really necessary.

That's a nice idea and that's why I basically added something like that to my CA system