The number of connected connections is how many DHT you can use on the DHT network to use link
BT also embedded in DHT network
faq: What is a public DHT (Hash Table) network based on KADEMLIA technology Intersection
Bit Elf (/) has supported the latest BT technology from V3: public DHT network based on KADEMLIA technology. Through the DHT network, BT users can download and upload normally without relying on traditional seed servers (). So what exactly is KADEMLIA technology and what is the public DHT network? It simply, Kademlia is just a technical standard (usually called the third -generation P2P technology), and DHT is the specific implementation of the technology. (For example, there is KAD implementation based on KADEMLIA technology). Kademlia is a P2P overlay protocol designed by Petar and David Mazières, for peer to peer computer networks. It specifies the structure of the network, regulates between nodes and how the exchange of has to take place. Kademlia nodes among using the transport protocol UDP ( see osi model). KADEMLIA NODES Store Data by Hash Table (DHT). Over An Existing Lan/Wan (like the Internet) a new, virtual network ). This number server not only as ites, but the kademlia algorithm used for further purposes. Specific technical details are not described here. Interested users can refer to relevant materials by themselves. So why do you introduce KADEMLIA -based public DHT networks in BT? In the traditional BT download, all seed files must specify one or more seed servers, which are usually called tracker or Announdce address. Once this seed server is used as a machine or stopped for other reasons (for example: our former service provider breach of the contract and forcibly unplug our server's network cable), BT users are likely to be unable to complete the upload and download of this seed file. In the traditional BT download, there are the following situations: there are two exactly the same seed files, but because different trackers are specified, users of different trackers cannot be downloaded and uploaded between users, so they cannot fully reflect the download/upload of BT efficiency. After the introduction of the public DHT network, even if the seed server is used as a machine (or the participation of the seed server at all), BT users can still get connecting through the DHT network to achieve download and uploading. So where are these connection information preserved? Simply put, these connection information is stored between DHT network participants (ie DHT nodes) selected according to certain algorithms, that is, once you join the public DHT network, you will have an ID (the ID is just a program. The generated, virtual, and completely random ID has no connection with your actual personal information, please rest assured), according to certain rules, you need to maintain the connection information of part of the seed file, which is equivalent to you at the same time and lightweight. Class seed server. Because some data communication flows are involved, it may have a slight burden or impact on your network. However, compared with the returns brought by the addition of the public DHT network, this impact can be ignored. It may have a large burden on your network: the seed file you are responsible for maintenance is exactly a very, very popular seed, such as thousands or even tens of thousands of BT users to download (if this situation is encountered, I strongly recommend that I strongly recommend You go to buy lottery tickets). Of course, from the perspective of psychological return, you are providing a bridge role for thousands of or even tens of thousands of BT users. This is a matter of pride and pride. Therefore, I strongly recommend that you open the public DHT network function in the Bit Elf (open default). Of course, if your network conditions are fragile or your service provider has made a lot of restrictions (easy to break the current), you can also be able The public DHT network function (personal settings-other options-allowing Bit Elf ...) to close the Bit Elf to prevent speeds from decreased. As mentioned earlier, the connection information is responsible for maintenance between each node, so is the more nodes connected by each BT user, the better? In fact, it is not, because the more network traffic and network burden brought by the more nodes will increase. Usually, there are 50 reliable nodes or 150 reliable nodes. The nodes and connection information you need to find. Therefore, under normal circumstances, when the program finds a certain node (such as 100 nodes), it will not actively find new nodes.
So the DHT network function of Bit Elf is different from the DHT network function of other BT clients? BT's KADEMLIA -based DHT network function is introduced by (Python) 4.1.0. A considerable algorithm optimization is much better in program performance, operating efficiency, and node positioning efficiency. In addition, the Bit Elf also comprehensively enhances the existing functions of the Bit Elf through the DHT network, such as the seed market. In addition, the Bit Elf even does not require the BT release site to provide the download of the seed file (it can greatly reduce the traffic pressure of the release station), and the traffic pressure of the release station is greatly reduced. And you can only provide a link similar to Kademlia/.. (40B hash Hex) .... (Tip: Select a task in the Bit Elf the link to).
In short, the introduction of the DHT network makes BT no longer necessary seed server. It can be said that the world has no service, but from a deeper perspective, it should be that the world has never been dissatisfied.
Your email address will not be published. Required fields are marked *
Save my name, email, and website in this browser for the next time I comment.