There is a simple way to relieve some stress of servents with no free upload slots :

Don't make them send out anny responses until upload slots are availble .

Now responses going trhu the servent will be unaffected ofcourse .

Allot of servents have auto-retry features including LimeWire .
Ive seen my LimeWire "under attack" of 17 different servents that tried to upload from me every 60 seconds .
Annoying to the least .

It would also reserve bandwidht on the network .
-less search results have to go through the network .
-Less bandwidht is waisted on servents tryng to make file tranfers off full servents .

Also this would be easy to implement since no changes have to be made to the protocol .

I deffinitly see this coming in future versions unless someone can find me a negative side of this idea .

Atleast say it sucks instead of ignoring me !

I think this idea is already there in a small sense; the quality stars have something to do with free upload slots. The query replies though should still go out but maybe the retry frequency should be different depending on how many stars the host had. Or the repeated requests could just leave one line of Upload Limit Reached in the upload section with a count of how many attempts were made.

Just ideas here, I think there is a problem that needs to be fixed. Unless bandwidth is that short I don't think query replies should be held back as an upload slot may open in a matter of minutes. The client end should figure out how to best deal with replies.

Adam's explanation of the quality stars in May, how this is done may have changed since then:
<http://www.gnutellaforums.com/showth...id=288#post778>