| | 1 | = Resume data = |
| | 2 | |
| | 3 | Using the functions ''torrent::Download::hash_check(true)'' and |
| | 4 | ''torrent::Download::hash_resume_save()'' the client can tell the |
| | 5 | library to load and save various data that is useful when resuming a |
| | 6 | download. To ignore resume data call |
| | 7 | ''torrent::Download::hash_check(true)''. |
| | 8 | |
| | 9 | The resume data is stored in the bencoded torrent as a dictionary |
| | 10 | under the key "libtorrent resume". All the following items are within |
| | 11 | that dictionary. |
| | 12 | |
| | 13 | == Completed chunks == |
| | 14 | |
| | 15 | When resuming the library will skip hash checking for chunk ranges |
| | 16 | that have valid resume data. The file modification time-stamp is |
| | 17 | stored with the resume data, and ranges containing files whose stored |
| | 18 | time-stamp does not exactly match what is on the disk it will be |
| | 19 | invalidated. If the file size does not match it will also invalidate |
| | 20 | the range. |
| | 21 | |
| | 22 | == Peer addresses == |
| | 23 | |
| | 24 | Peer addresses that are contained in torrent::AvailableList will be |
| | 25 | saved, which will includes connected peers as their addresses are |
| | 26 | copied over when a torrent is stopped. |
| | 27 | |
| | 28 | == Files == |
| | 29 | |
| | 30 | Various file related information is stored in a list under the key |
| | 31 | "files". This list exactly matches the file list in the original |
| | 32 | torrent. |
| | 33 | |
| | 34 | * ''mtime'': File modification time-stamp as an integer. |
| | 35 | * ''priority'': The file priority as an integer between [0,3>. |
