diff --git a/docs/manual.html b/docs/manual.html index c666d2ab2..c6dc41de0 100644 --- a/docs/manual.html +++ b/docs/manual.html @@ -44,214 +44,215 @@
Table of contents
fail_limit is the max number of failures to announce to this tracker in +a row, before this tracker is not used anymore.
+fails is the number of times in a row we have failed to announce to this +tracker.
+source is a bitmask specifying which sources we got this tracker from.
+verified is set to true the first time we receive a valid response +from this tracker.
+updating is true while we're waiting for a response from the tracker.
+start_sent is set to true when we get a valid response from an announce +with event=started. If it is set, we won't send start in the subsequent +announces.
+complete_sent is set to true when we send a event=completed.
+++void rename_file(int index, boost::filesystem::path) const; ++
Renames the file with the given index asynchronously. The rename operation is complete +when either a file_renamed_alert or file_rename_failed_alert is posted.
+@@ -2127,12 +2168,13 @@ void set_tracker_login(std::string const& usernameset_tracker_login() sets a username and password that will be sent along in the HTTP-request of the tracker announce. Set this if the tracker requires authorization.
std::vector<announce_entry> const& trackers() const; void replace_trackers(std::vector<announce_entry> const&) const; +void add_tracker(announc_entry const& url);
trackers() will return the list of trackers for this torrent. The @@ -2143,6 +2185,9 @@ trackers for this torrent, you can use trackers() and will replace it. If you want an immediate effect, you have to call force_reannounce().
+add_tracker() will look if the specified tracker is already in the set. +If it is, it doesn't do anything. If it's not in the current set of trackers, +it will insert it in the tier specified in the announce_entry.
user_agent this is the client identification to the tracker. @@ -3303,6 +3350,13 @@ is so that newly started torrents are not considered inactive until they have a fair chance to start downloading.
If rate_limit_ip_overhead is set to true, the estimated TCP/IP overhead is drained from the rate limiters, to avoid exceeding the limits with the total traffic
+announce_to_all_trackers controls how multi tracker torrents are +treated. If this is set to true, all trackers in the same tier are +announced to in parallel. If all trackers in tier 0 fails, all trackers +in tier 1 are announced as well. This is the uTorrent behavior. If it's +set to false, the behavior is as defined by the multi tracker +specification. It defaults to false, which is the same behavior previous +versions of libtorrent has had as well.
The function should return the hash of the piece stored in the slot.