diff --git a/docs/manual.html b/docs/manual.html index 125b96242..8a308e77b 100644 --- a/docs/manual.html +++ b/docs/manual.html @@ -46,213 +46,213 @@

Table of contents

@@ -459,12 +459,11 @@ timeout can be set with set_setti

pause() resume() is_paused()

-
-
::
-
void pause(); +
+void pause();
 void resume();
-bool is_paused() const;
-
+bool is_paused() const; +

Pausing the session has the same effect as pausing every torrent in it. Resuming will restore the torrents to their previous paused state. i.e. the session pause @@ -554,9 +553,12 @@ There are 3 different modes:

All pieces will be written to the place where they belong and sparse files will be used. This is the recommended, and default mode.
storage_mode_allocate
-
All pieces will be allocated, zeroes will be written to the files, before -the data is downloaded and written to the file. This might be useful for -filesystems that don't support sparse files.
+
Same as storage_mode_sparse except that files will be ftruncated on +startup (SetEndOfFile() on windows). For filesystem that supports sparse +files, this is in all practical aspects identical to sparse mode. For +filesystems that don't, it will allocate the data for the files. The mac +filesystem HFS+ doesn't support sparse files, it will allocate the files +with zeroes.
storage_mode_compact
The storage will grow as more pieces are downloaded, and pieces are rearranged to finally be in their correct places once the entire torrent has been @@ -769,6 +771,9 @@ struct session_status int num_unchoked; int allowed_upload_slots; + int optimistic_unchoke_counter; + int unchoke_counter; + int dht_nodes; int dht_cache_nodes; int dht_torrents; @@ -806,6 +811,10 @@ than the sum of all peers of all torrents because the incoming connections may n be assigned a torrent yet.

num_unchoked is the current number of unchoked peers. allowed_upload_slots is the current allowed number of unchoked peers.

+

optimistic_unchoke_counter and unchoke_counter tells the number of +seconds until the next optimistic unchoke change and the start of the next +unchoke interval. These numbers may be reset prematurely if a peer that is +unchoked disconnects or becomes notinterested.

dht_nodes, dht_cache_nodes and dht_torrents are only available when built with DHT support. They are all set to 0 if the DHT isn't running. When the DHT is running, dht_nodes is set to the number of nodes in the routing @@ -2998,7 +3007,7 @@ struct session_settings bool lazy_bitfields; int inactivity_timeout; int unchoke_interval; - int optimistic_unchoke_multiplier; + int optimistic_unchoke_interval; address announce_ip; int num_want; int initial_picker_threshold; @@ -3136,8 +3145,8 @@ Default is 10 minutes

On this interval, peers are re-evaluated for being choked/unchoked. This is defined as 30 seconds in the protocol, and it should be significantly longer than what it takes for TCP to ramp up to it's max rate.

-

optimistic_unchoke_multiplier is the number of unchoke intervals between -each optimistic unchoke interval. On this timer, the currently optimistically +

optimistic_unchoke_interval is the number of seconds between +each optimistic unchoke. On this timer, the currently optimistically unchoked peer will change.

announce_ip is the ip address passed along to trackers as the &ip= parameter. If left as the default (default constructed), that parameter is ommited.

@@ -5098,7 +5107,9 @@ scripts.

Thanks to Reimond Retz for bugfixes, suggestions and testing

Thanks to University of Umeå for providing development and test hardware.

Project is hosted by sourceforge.

-

sf_logo

+