>--[Rafael R. Reilova]--<[EMAIL PROTECTED]>

> 1. First we are probably hammering the web cache if we don't connect 
> quickly enough to some ultrapeers (one query per sec. I believe) 

*nod* (I've seen this happen, if the host cache is empty and the only
reachable webcache lists only hosts being offline)

> 1> store the time of the last hit to the webcache and don't hit again until 
> some reasonable amount of time has elapsed, say 2-5 minutes? This forces 
> gtk-gnutella to eat up some of those unreachable hosts in the cache, 
> hopefully hitting a good host in the process. 

Actually my mingW pacthes include something like that, it selects a web
cache only once every whatever time (but hits it 8 times in a row, though).

The web cache protocol allows only one request per hour; Web caches are
often configured to start banning if the request is after less than 55
minutes. So Gtk-Gnutella violates the web cache protocol.

-- 
         100 DM =  51  � 13 �.
         100  � = 195 DM 58 pf.
  mailto:[EMAIL PROTECTED]
    http://www.ruediger-kuhlmann.de/


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Gtk-gnutella-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel

Reply via email to