Quoting Alex Bennee <[EMAIL PROTECTED]> from ml.softs.gtk-gnutella.devel: :I appreciate you shouldn't have to do that. However my experience is if :you've been down for a few days GTKG will spend hours going through a :whole load of dead clients in its huge cache. This affects connection time :to the network greatly, especially as some routers are limited in how many :simultaneous connections they can maintain. Typically your waiting for :many connections to timeout rather than be explicitly closed.
We should really process GGEP "DA" extensions in pongs (I think it stands for Daily Average uptime) and store that in the cache. That would allow us to pick-up the hosts that are more likely to be alive. I think it's been in my TODO list for over 2 years now. But other more important things keep coming up. GTKG currently suffers from lack of development manpower. It shows in some areas, and that's why we still lack TTH or have a sub-optimal bootstrapping procedure. I don't personally suffer from those and therefore tend to under-prioritize them. Raphael ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
