Re: Upload queue idea: Candidate selection based on on the response ratioDate: Thu, 4 Sep 2008 21:53:24 +0000 (UTC)

Quoting Arne Babenhauserheide <[email protected]> from ml.gnutella.dev-forum:
:> Note this has nothing to do with the file size.  You can request 20 KiB of
:> a 2 GiB file, it's still a small request.
:
:This is dangerous, because it provides an incentive for abusive behaviour: 
:Request files in little pieces when you see that a source has a full queue, so 
:I wouldn't open that hole. 

Well, it's not dangerous if you're careful, and gtk-gnutella is careful
enough to remember the total size of "small requests" that are allowed
to bypass.  After some threshold, you go back to the queue so you can't
really abuse the system because only so many bytes can be served that way
to a given host.

:If there is a weakness, someone will exploit it, and the users will applaud 
:because of the great speeds - till the whole network goes down, and they with 
:it. 

Which is why there is precisely no weakness in the implementation. :-)

:But if it wasn't for that hole, the feature would be very useful. 

Thanks!

:> Finally, clients should make sure download mesh exchanges take place during
:> the queuing exchanges.  It is useless to wait for the actual transfer to
:> take place to start exchanging sources.
:
:Isn't that standard behaviour? That's why queued sources are still useful if 
:they never make it through the queue, because they finish before reaching the 
:end of the queue :) 

I'm not sure every servent out there does that.  But it's been a long time
since I last checked.

Raphael