Quote:
Originally posted by trap_jaw2
LimeWire will have trouble if that connection ever fails because it will very likely try to obtain new addresses from the public GWebcaches (you can't shut that off in the options). The number of connections an ultrapeer tries to maintain is far too high for a private network.
|
I think it work like this, you manually add a local IP-adress and Port number which not have to be 6345 can be any other, then this adress is set up, Limewire closes connection view window by turning the CONNECTION_VIEW_ENABLED=false instead of true
as it is in .limeprops file. This will stop Limewire from aquire adresses from Gwebcache.
Quote:
|
Routing search results is very expensive. - And a total of 150 (or was it 240?) search results is more than enough. I assume it's even better for the network if a user issues more queries instead of getting more results per search because he is forced to be more specific when entering search keywords.
|
However it is, im not satisfied with the search performance of Limewire, it havent change to the better with the new versions here. And again since i mentioned this before I think Limewire have pulled this minimize to the extreme network traffic too far
also due to the fact the majority now sits on broadband not typ 56 k modems any more. So this minimized net traffic profil suites Intranets very well, think about it.
Quote:
|
That is strange, GnucDNA based servents usually are using old TTL 7 ......When searching with GnucDNA based servents you should
|
A correction here I meant Mutella and MyNapster, Mutella is worst concerning shield me from this clients traffic the dropped I/0 with 0 drops. Oh! i have an Gnucleus 1.8.4.0 right now status right now is 13 percent, My next host is Limewire latest 2.9.1.0 holds with 93 percent, so you seing the difference here. This also gives a fingerpointing to why Limewire shield of traffic so well, thats before it shall be used in Intranets