The constructor that takes an info-hash will initialize the info-hash to the given value, @@ -1478,6 +1494,11 @@ initialize the torrent_info object for you.
The version that takes a filename will simply load the torrent file and decode it inside the constructor, for convenience. This might not be the most suitable for applications that want to be able to report detailed errors on what might go wrong.
+The overloads that takes an error_code const& never throws if an error occur, they +will simply set the error code to describe what went wrong and not fully initialize the +torrent_info object. The overloads that do not take the extra error_code parameter will +always throw if an error occurs. These overloads are not available when building without +exception support.
libtorrent uses boost.system's error_code class to represent errors. libtorrent has +its own error category (libtorrent::libtorrent_category) whith the following error +codes:
+| code | +symbol | +description | +
|---|---|---|
| 0 | +no_error | +Not an error | +
| 1 | +file_collision | +Two torrents has files which end up overwriting each other | +
| 2 | +failed_hash_check | +A piece did not match its piece hash | +
| 3 | +torrent_is_no_dict | +The .torrent file does not contain a bencoded dictionary at +its top level | +
| 4 | +torrent_missing_info | +The .torrent file does not have an info dictionary | +
| 5 | +torrent_info_no_dict | +The .torrent file's info entry is not a dictionary | +
| 6 | +torrent_missing_piece_length | +The .torrent file does not have a piece length entry | +
| 7 | +torrent_missing_name | +The .torrent file does not have a name entry | +
| 8 | +torrent_invalid_name | +The .torrent file's name entry is invalid | +
| 9 | +torrent_invalid_length | +The length of a file, or of the whole .torrent file is invalid. +Either negative or not an integer | +
| 10 | +torrent_file_parse_failed | +Failed to parse a file entry in the .torrent | +
| 11 | +torrent_missing_pieces | +The pieces field is missing or invalid in the .torrent file | +
| 12 | +torrent_invalid_hashes | +The pieces string has incorrect length | +
| 13 | +too_many_pieces_in_torrent | +The .torrent file has more pieces than is supported by libtorrent | +
| 14 | +invalid_swarm_metadata | +The metadata (.torrent file) that was received from the swarm +matched the info-hash, but failed to be parsed | +
| 15 | +invalid_bencoding | +The file or buffer is not correctly bencoded | +
The names of these error codes are declared in then libtorrent::errors namespace.
+The storage interface is a pure virtual class that can be implemented to @@ -4789,6 +4900,7 @@ struct storage_interface virtual bool initialize(bool allocate_files) = 0; virtual int readv(file::iovec_t const* bufs, int slot, int offset, int num_bufs) = 0; virtual int writev(file::iovec_t const* bufs, int slot, int offset, int num_bufs) = 0; + virtual int sparse_end(int start) const; virtual bool move_storage(fs::path save_path) = 0; virtual bool verify_resume_data(lazy_entry const& rd, std::string& error) = 0; virtual bool write_resume_data(entry& rd) const = 0; @@ -4851,6 +4963,18 @@ exceptions when it's not. Specifically if the read cache is disabled/or full and client requests unaligned data, or the file itself is not aligned in the torrent. Most clients request aligned data.
+++int sparse_end(int start) const; ++
This function is optional. It is supposed to return the first piece, starting at +start that is fully contained within a data-region on disk (i.e. non-sparse +region). The purpose of this is to skip parts of files that can be known to contain +zeros when checking files.
+