On Saturday 27 November 2004 02:17, Haxe wrote: > Ah, now I think I know what's up. > 80% of my incoming queries are dropped due to > "Max TTL exceeded"! I think this is the whole problem.
Ok, that's it. Until yesterday, 80% of the incoming queries were dropped. With today's latest update of share.c only 50% are dropped, and everything works a bit better now. But that's still very much. 50% are still dropped due to "Max TTL exceeded". Aren't other servents such as Limewire and BearShare supposed to send queries with a sane TTL that won't cause them to be dropped? I mean, 50%, duh... I think it's a bit hard to simply drop Queries with a bit too high TTL. An intermittent UP should of course clip that TTL to a max value. But I am not a UP, I am a leaf node. The Query has successfully reached my host. Why not process it and answer with an according TTL so that the QHit will also reach its destination? If it were only for 1%, I'd agree to simply drop. But we are talking about 50% here. That's rough. Haxe ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
