Quote:
|
But more results isn't always good. Especially given that LimeWire can't filter ports.
|
LimeWire can if you can.
Quote:
|
An Ultrapeer connection blinds the client to the realities of possible or impossible connections.
|
WHAT??? I don't know what you mean, but I'm almost certain you got something wrong.
Quote:
|
With 0.6 connections a greater percentage (still not all, but MUCH more) of the queryhits you get are from hosts that you can actually connect to, because obviously if you got the queryhit you can exchange data with that host.
|
Not at all. A client with a 0.6 connection can return queryhits without ever being able to accept incoming connections (= being firewalled).
Quote:
|
Funneling everything in and out via an UP means that more queryhits are returned, but most of the leaves of an average Ultrapeer are inaccesible to me.
|
So you are behind a firewall and don't want to receive results from other firewalled hosts??? 0.6 connections won't help you in that case.
Quote:
|
Getting queryhits bounced off of an Ultrapeer only means that both the host in question and myself can connect to the Ultrapeer. The fact that the Ultrapeer allows me to get queryhits from these hosts is of little consequence in terms of being able to access the hosts themselves, because the actual business of requests and transfers is handled directly between me and the host in question.
|
First, what you are saying about Ultrapeers is true for every other gnutella host two. If a host A is connected to a host B, it does NOT mean A accepts incoming connections. - But that doesn't matter, because there is the PUSH request.
Quote:
|
With a 0.6 connection, a much greater percentage of my search horizon is made up of hosts I can get to.[...]
|
That would surprise me indeed, - since the amount of firewalled users is about the same, no matter what clients they use. And you can download from any of them unless you don't accept incoming connections either.