 | This article has not yet been rated on Wikipedia's content assessment scale. |
Discuss differences between Kademlia and Mainline DHT
editDiscuss differences between Kademlia and Mainline DHT
- Not all nodes that we learn about are equal. Some are "good" and some are not. Many nodes using the DHT are able to send queries and receive responses, but are not able to respond to queries from other nodes. It is important that each node's routing table must contain only known good nodes. A good node is a node has responded to one of our queries within the last 15 minutes. A node is also good if it has ever responded to one of our queries and has sent us a query within the last 15 minutes. After 15 minutes of inactivity, a node becomes questionable. Nodes become bad when they fail to respond to multiple queries in a row. Nodes that we know are good are given priority over nodes with unknown status.
- The usage of tokens
- The usage of ports as well as addresses
- get_peers - After the search is exhausted, the client then inserts the peer contact information for itself onto the responding nodes with IDs closest to the infohash of the torrent.
- Usage of bucket splitting (saves space)