This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links [2011/07/22 12:08] greywizard [Tracker] |
peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links [2011/07/22 12:08] greywizard [Torrent] |
||
---|---|---|---|
Line 60: | Line 60: | ||
===Hash-check=== | ===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).\\ | + | 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.\\ | 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.\\ |