Quote:
Originally posted by Neko-Yasha
Some of the stuff mentioned here really couldn't be done without support in all other clients. |
Everything I've (me) talked about can be done. As I stated "tweaks" to LimeWire to get optimal performance out of the network (filtering unneccessary data inout and output).
Quote:
Also a note about freeloaders, a peer may not accept incoming connections because it's behind a firewall or it's just full (the listener won't accept any new connections). Neither of these make them freeloaders. |
Full hosts are not a problem b/c you (user) would not be connected to them so it wouldnt matter. I also rather get a firewalled host b/c their higher connections so that means a bigger horizon. Which also means they wouldnt matter b/c you can still send queries to the hosts their connected too. If you were speaking of the statement I made about disconnecting hosts that do not have a certain number of hosts for a certain duration, well that has happen to me quit a few times. One time this one host was connected for ~5 mins and their host count was zero. I'm guessing that happens when someone only has one connection opened (which is only you) or cant establish a connection to other hosts for some reason. It being a bandwidth or whatever else. That host should be disconnect b/c it creates a bottle for the user connected to them.
Quote:
[B]
The only way to kill a freeloader is to not allow them to connect to you (g-net connections not download). g-net doesn't include this info with download attempts, and trying to then connect back to the host just creates extra traffic and really tells you nothing.
[B]
|
Freeloaders have to start some where. Then again I do believe any new user (the average joe) has something to share for the first time using the gnutella network.