Options.Gnutella: Difference between revisions
(Inserting Template:Languages) |
m (1 revision) |
Revision as of 20:11, 20 June 2009
 Languages: |
[[::Options.Gnutella|English]] • [[::Options.Gnutella/de|Deutsch]] • [[::Options.Gnutella/es|Español]] • [[::Options.Gnutella/fr|Français]] • [[::Options.Gnutella/he|עברית]] • [[::Options.Gnutella/it|Italiano]] • [[::Options.Gnutella/nl|Nederlands]] • [[::Options.Gnutella/pl|Polski]] • [[::Options.Gnutella/pt|Português]] • [[::Options.Gnutella/ru|Русский]] • [[::Options.Gnutella/zh-hant|中文(繁體)]] | e |
Gnutella Network options
- Connect to Gnutella2 today
Shareaza will always connect to the Gnutella2 network if this is turned on. (recommended)
- Connect to Gnutella1 today
Shareaza will connect to the Gnutella1 network only for this session. This will be turned off again if you restart Shareaza.
- Always connect to Gnutella1
Shareaza will always connect to The Gnutella1 network.
- Allow this node to become a Hub
Your computer becomes a Hub if one is needed by the network and if you have sufficient system requirements. A Hub connects to other Hubs and Gnutella Ultrapeers and forwards all search queries it receives to all other Peers. Additionally clients running in leaf mode can connect to an Ultrapeer. Leaf nodes don't have any other nodes attached and therefore generate very low traffic (they only transmit their own queries). But the most important thing is, that leaf nodes don't get all search queries from the Hub but only the ones they are very likely to have. The Hub can decide this by using a query routing table which is available for every attached leaf. Only enable this if you have 256 kbit/s or more upstream. If your connection or computer can't handle it you will lose download speed.
If you want to know more about this, go here:
- Force this node to be a Hub
You computer will always become a Hub, if the network needs one. You will even be a Hub if Shareaza "thinks", that your connection is too slow. Only check this if you know what you are doing, you must have enough bandwidth (>256 kbit/s upstream) and CPU power. You won't get better results if you check this. There is really no need to check this because you want better search results. You'll only harm the network if you lack the bandwidth and CPU power to be a Hub.
You'll have to disconnect and reconnect (or restart Shareaza) for this option to take effect.
- Allow this node to become a leaf
Your Computer may act as a Leaf (described above). Don't uncheck this, unless you want your computer to be an old style peer. You will have to uncheck "Allow this node to be a Hub" as well. You will have trouble connecting to both G1 and G2 if you uncheck this.
Accept only Hub connections This forces Shareaza to be a leaf node only. So that it will always be shielded from all the unnecessary network traffic by a Hub. However this option is obsolete since there are almost no not UP capable nodes on the network.
Link compression
Shareaza uses the Zlib library to compress network traffic in order to save some bandwidth. There is usually no reason to disable this function. If you are running Shareaza on a very old, slow computer, you may wish to disable this function because compression uses some CPU power, however for most users saving bandwidth is a good trade-off for slight increases in CPU use.
Gnutella-G2
Leaf to Hub: Sets the number of hub(s) connections that Shareaza will use. Hubs are computers in the network that were chosen to help it work, a Hub is the one that connects you to the network and takes care of all the searching. On Gnutella2, there is no need to connect to more than 2 hubs. If you connect to more it will only damage the network.
Hub to Leaf: This is the number of leafs that can connect to you if you are a Hub. 400 is the default. For many computers this is too much, so you might want to lower this if your computer becomes really laggy if running in hub-mode.
Hub to Hub: This is the number of connections that will be made to other Hubs if you are a Hub. More is always better here, but only if you can handle the traffic. If you have 256 Kbit/s upstream you can handle about 5 Hub to Hub connections. If you have more bandwidth it is more.
Gnutella-G1
These are generally the same as for G2.
Leaf to Hub: This number should be set to either 1 or 2 if you are connecting to Gnutella. The maximum allowable number is 2. This is to prevent abuse of the network.
Hub to Leaf: If you have Gnutella1 enabled and you're running in hub mode you should also allow some G1 leaves to connect. 50 should be a good number for that.
Hub to Hub: G1 UP to G2 hub connections don't work very well and some Gnutella1 Clients don't allow this kind of connection anyway, so you might want to set this to 0.
New Settings page
Gnutella Networks Options page replacement:
Gnutella Network Options
Gnutella2 Network
Connect to Gnutella2 today By default, this setting is checked. Mode Leaf or Hub. Each user on the Gnutella and G2 networks is known as a Node. Leaves are the most common type of Node: they are those that allow their library to be catalogued on their connected Hubs, and upload and download files from other Leaves. If you have sufficient bandwidth, CPU, computer memory and a modern OS, Shareaza may elect you to be a G2 Hub. Hubs connect to several hundred G2 Leaves and a few other Hubs. Windows98 and WindowsME users do not have the ability to become a Hub, since those operating systems cannot adequately handle the high number of tcp connections necessary for good Hub performance. Those interested in details about the function of Hubs and the G2 Network architecture in general should refer to the Gnutella2 protocol.
Gnutella1 Network
Always connect to Gnutella1 If you want to always connect to Gnutella, this setting can be checked. By default, it is unchecked. Connect to Gnutella1 today By default unchecked, if you decide to connect to Gnutella (see the networks menu), it will check itself. Mode Leaf or Hub. Again, Win98 and WinME users have no choice but to be a Leaf. Shareaza's Ultrapeer (Hub) support for Gnutella is still considered to be in the development stage. You can read more about Ultrapeer specification in the Gnutella Development Forum.
G2 Connections
Leaf to Hub The setting can be 1, 2 or 3. The default is two, but one is usually sufficient. Hub to Leaf The value can be 0 to 1024. This defines the maximum number of Leaves your Hub will allow to connect. Larger numbers of Leaves require more bandwidth, along with more cpu and memory capabilities from your computer. A typical number of Leaves to allow is 200 to 300. Hub to Hub The value can be 0 to 128. If your Node is a Hub, it defines the maximum number of connections to be made to other Hubs.
G1 Connections
Leaf to Ultrapeer The value may be 1 or 2. Defines how many Ultrapeers your Leaf will connect to. The default is one, which is sufficient. Ultrapeers allow Shareaza to search the Gnutella network, and allow other users on Gnutella to find files your node is sharing. Ultrapeer to Leaf The value may be 0 to 1024. If your Node is an Ultrapeer, this defines the maximum number Leaves which will be allowed to connect. A typical number is 80 to 300. Peer to Peer The value may be 0 to 128, which defines the maximum number of Ultrapeers to which you will make connections if your Node is elected to be an Ultrapeer.
Link Compression
Shareaza uses the Zlib library to compress network traffic in order to save some bandwidth. There is usually no reason to disable this function. If Shareaza is running on a very old, slow computer, this compression function may be disabled to save some CPU cycles. However for most users saving bandwidth is a good trade-off for slight increases in CPU use.
--Question-- is it Zlib or is it deflate for link Compression: Deflate, I thought ? please edit when the answer is clear :-)