Question: Locally generated queries are currently passed to the dynamic query code. Subsequently, queries are no longer sent when more results have been generated than a hard-coded limit, currently 150. Is this intentional behavior, or has a query reply limit (for when we receive queries from other sources and generate dynamic queries) been misapplied? If intentional, should this value be a parameter rather than hard-coded?
Suggestion: That the current probability-based rejection of hosts for caching with ports 6346-6350 be replaced with a preferences parameter governing %age of connections allowed to such ports, as per peer type, et cetera. The current hardcoded setting makes caching too improbable for discovery of BearShare clients. These seem to be less densely locally connected than LimeWire or Frosty, and are useful at the least for host discovery. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
