added missing documentation of stop_tracker_timeout in session_settings
This commit is contained in:
parent
883773e8fa
commit
3e4ee68e66
|
@ -2164,6 +2164,7 @@ that will be sent to the tracker. The user-agent is a good way to identify your
|
||||||
std::string user_agent;
|
std::string user_agent;
|
||||||
int tracker_completion_timeout;
|
int tracker_completion_timeout;
|
||||||
int tracker_receive_timeout;
|
int tracker_receive_timeout;
|
||||||
|
int stop_tracker_timeout;
|
||||||
int tracker_maximum_response_length;
|
int tracker_maximum_response_length;
|
||||||
|
|
||||||
int piece_timeout;
|
int piece_timeout;
|
||||||
|
@ -2198,6 +2199,10 @@ seconds, the tracker will be considered as having timed out. If a tracker
|
||||||
is down, this is the kind of timeout that will occur. The default value
|
is down, this is the kind of timeout that will occur. The default value
|
||||||
is 20 seconds.
|
is 20 seconds.
|
||||||
|
|
||||||
|
``stop_tracker_timeout`` is the time to wait for tracker responses when
|
||||||
|
shutting down the session object. This is given in seconds. Default is
|
||||||
|
10 seconds.
|
||||||
|
|
||||||
``tracker_maximum_response_length`` is the maximum number of bytes in a
|
``tracker_maximum_response_length`` is the maximum number of bytes in a
|
||||||
tracker response. If a response size passes this number it will be rejected
|
tracker response. If a response size passes this number it will be rejected
|
||||||
and the connection will be closed. On gzipped responses this size is measured
|
and the connection will be closed. On gzipped responses this size is measured
|
||||||
|
|
Loading…
Reference in New Issue