![]() ![]() That represents how many effective copies there are of a torrent. Look at the "distributed copies" number your client gives you. The cause of your problem is likely that your torrent ran out of seeds before you finished downloading. It's not something that users can turn on or off, it's an integral part of the protocol. What this has to do with PAR2s are obvious: the entire effective functionality of PAR2s is already integrated into BT, automatically. Some clients will also check the file after you download it, just to make sure it's been written to disk properly. Most clients will also check the entire file when you go to resume a download, so it can determine what pieces it needs to (re-)download. the checksums don't match - it redownloads the chunk. As each chunk arrives, it's checked by your BT client. torrent files are much larger than others (smaller chunk size, more chunks, more checksums to include in the file). Each chunk gets a checksum which is, I believe, included in the. It then splits this pseudo-file up into many chunks of configurable size. ![]() Well, basically what BT does is treat all torrents as single files (even if one torrent includes many files).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |