![]() ![]() Once your peers know a few peers from the DHT, your client will ask those peers for the information about making a connection to other peers. This makes it possible for peers to know each other quickly, without the need for a tracker or DHT to ask requests. When these peers are uploading/downloading a particular torrent, they try to tell each other about all of the other peers they know of that are participating in the same torrent swarm. To do so, it needs to notify these clients that it would like to participate in the swarm and ask them for the connection information of peers they already know of, that are participating in the swarm. It can also participate in a swarm by searching the DHT network for several other clients whose IDs are as close as possible to the infohash. ![]() ![]() Once it has gotten into the network of peers, your torrent client doesn’t need that bootstrap node anymore. Usually, the client has a bootstrap node built in to start with. It then uses bootstrap as its connection to the DHT network using either hard-coded addresses of clients controlled by the torrent client developer, or using the DHT-supporting clients that were previously encountered in a torrent swarm. When a torrent client joins the DHT network for the first time, it generates a random 160-bit ID from the same space as infohashes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |