Home

A free C++ BitTorrent/HTTP/FTP Download Client

peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links [2011/07/17 20:53]
greywizard [Seeds and Seeding] - expanded a bit, explanation of seeding
peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links [2011/07/22 12:08]
greywizard [Torrent]
Line 26: Line 26:
 Nevertheless, if every client who completed a download would remove the task as soon as finished, that torrent would pretty soon be dead. Therefore, seeding is a **paramount** activity on the BitTorrent Network; it's what makes it work and what gives **you** the possibility to find all those files you seek. Nevertheless, if every client who completed a download would remove the task as soon as finished, that torrent would pretty soon be dead. Therefore, seeding is a **paramount** activity on the BitTorrent Network; it's what makes it work and what gives **you** the possibility to find all those files you seek.
  
-Therefore, in order to share with others what you have downloaded, just leave the task running in your client until it reaches at least a 1.5 - 2.0 share ratio. Also in BitComet another technology called Long-Term Seeding will make sure that any present task even if stopped (i.e. inactive) will still upload towards other BitComet peers through the means of LT-Seeding protocol, which is proprietary to BitComet, provided there is available unused upload bandwidth, that LT-Seeding is enabled globally on you client as well as on that particular task (which is the case by default) and that the torrent isn't private.\\ +Therefore, in order to share with others what you have downloaded, just leave the task running in your client until it reaches at least a 1.5 - 2.0 share ratio. Also in BitCometanother technology called [[long-term_seeding|Long-Term Seeding]] will make sure that any present task even if stopped (i.e. inactive) will still upload towards other BitComet peers through the means of LT-Seeding protocol, which is proprietary to BitComet, provided there is available unused upload bandwidth, that LT-Seeding is enabled globally on you client as well as on that particular task (which is the case by default) and that the torrent isn't private.\\ 
 Bottom line, as long as the task is present in the Task List of BitComet in a state or another it's a good chance it's still uploading. Bottom line, as long as the task is present in the Task List of BitComet in a state or another it's a good chance it's still uploading.
 +
 +On the other hand, if you mean to share with others files which you have on your local storage media but which are not described by tasks already present in your Task List, then you should look into making and uploading torrents into the BitTorrent Network. For that you can find a pretty detailed guide here: [[making_torrents_with_bitcomet|Making torrents with BitComet]].
  
 ===Super-seeding (initial seeding)=== ===Super-seeding (initial seeding)===
Line 55: Line 57:
  
 Transfers in the BitTorrent Network, use pieces as trading units. The torrent making application, upon creation of the //.torrent// file, virtually concatenates together all the files of the torrent and then splits the resulted data chunk in pieces of equal size (usually between 64KB and 4MB). For each piece a [[wp>SHA-1]] hash-value is calculated, which is then put in the //.torrent// file. When another peer receives a piece later, it calculates the hash value for it, using the same algorithm, and compares that to the value recorded in the //.torrent// file, in order to check the piece’s data integrity. Transfers in the BitTorrent Network, use pieces as trading units. The torrent making application, upon creation of the //.torrent// file, virtually concatenates together all the files of the torrent and then splits the resulted data chunk in pieces of equal size (usually between 64KB and 4MB). For each piece a [[wp>SHA-1]] hash-value is calculated, which is then put in the //.torrent// file. When another peer receives a piece later, it calculates the hash value for it, using the same algorithm, and compares that to the value recorded in the //.torrent// file, in order to check the piece’s data integrity.
 +
 +===Hash-check===
 +
 +Many clients will perform an integrity check upon the complete download of all pieces for a task. This consists of the same procedure as the one described above, except this time the client will calculate the hash value for each downloaded piece for that task and compare it against the expected value, which is already written inside the //.torrent// file. Any piece which doesn' pass the hash check will be discarded, as it's considered corrupted (that could happen either during transport or even at source).\\ 
 +
 +This same procedure can be initiated manually, by the user usually by right-clicking the task and choosing the option to hash-check from the context menu.\\ 
 +In BitComet this option is called "Manual Hash Check".
  
 ---- ----
Line 66: Line 75:
 Basically, the tracker is a service which responds to HTTP GET requests. The requests include metrics from clients that help the tracker keep overall statistics about the torrent. The response includes a peer list that helps the client participate in the torrent. The base URL consists of the "announce URL" as defined in the metadata (//.torrent//) file. The parameters are then added to this URL, using standard CGI methods. Basically, the tracker is a service which responds to HTTP GET requests. The requests include metrics from clients that help the tracker keep overall statistics about the torrent. The response includes a peer list that helps the client participate in the torrent. The base URL consists of the "announce URL" as defined in the metadata (//.torrent//) file. The parameters are then added to this URL, using standard CGI methods.
  
-A tracker server should be differentiated from a BitTorrent index server. A BitTorrent index is a list of //.torrent// files, usually including descriptions and other information. Trackers merely coordinate communication between peers attempting to download the payload of the torrents.+A tracker server should not be mistaken with and should be differentiated from a **BitTorrent index server**. A **BitTorrent index** is a server which contains a list of //.torrent// files, usually including descriptions and other information and which will serve the actual //.torrent// files to anyone who will choose to download something from the list.\\  
 +Trackers merely coordinate communication between peers attempting to download the payload of the torrents.
  
 Many BitTorrent websites act as both tracker and index. Sites such as these publicize the tracker's URL and allow users to publish (upload) torrents to the index with the tracker's URL embedded in them, providing all the features necessary to initiate a download. Many BitTorrent websites act as both tracker and index. Sites such as these publicize the tracker's URL and allow users to publish (upload) torrents to the index with the tracker's URL embedded in them, providing all the features necessary to initiate a download.
 
peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links.txt · Last modified: 2015/08/15 04:21 (external edit)
[unknown button type]
 
Recent changes RSS feed Driven by DokuWiki