I've noticed on some downloads my download queue rapidly fills up with alternate locations but a lot of them fail with "Timeout" or "Connection Refused [No Push]" (despite having set "Never send a push request").
Over time these all fill up and slowly regurgitate, the only way to stop them cycling seems to be to freeze the queue and manually remove all the timeout entries. It seems to me that most timeouts are probably clients that are just no longer there and the best thing to do would be to dump these quickly (maybe only after 2 retries or something). Am I correct with the assumption that most modern clients will at least respond to a request with a "File not found" or "Busy" response? -- Alex http://www.bennee.com/~alex/ ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
