change defaults for rate_limit_utp setting

This commit is contained in:
arvidn 2017-12-16 17:53:20 +01:00 committed by Arvid Norberg
parent 96bf0ad5de
commit 0848d9b7f5
2 changed files with 10 additions and 1 deletions

View File

@ -50,6 +50,15 @@ The flags ``flag_override_resume_data``, ``flag_merge_resume_trackers``, ``flag_
The old API is still supported as long as libtorrent is built with deprecated functions enabled (which is the default).
It will be performing slightly better without deprecated functions present.
rate_limit_utp changed defaults
===============================
The setting ``rate_limit_utp`` was deprecated in libtorrent 1.1.
When building without deprecated features (``deprecated-functions=off``) the default behavior also changed to have rate limits apply to utp sockets also.
In order to be more consistent between the two build configurations, the default value has changed to true.
The new mechanism provided to apply special rate limiting rules is *peer classes*.
In order to implement the old behavior of not rate limiting uTP peers, one cans set up a peer class for all uTP peers, to make the normal peer classes not apply to them (which is where the rate limits are set).
announce entry multi-home support
=================================

View File

@ -171,7 +171,7 @@ constexpr int CLOSE_FILE_INTERVAL = 0;
SET(no_recheck_incomplete_resume, false, nullptr),
SET(anonymous_mode, false, &session_impl::update_anonymous_mode),
SET(report_web_seed_downloads, true, &session_impl::update_report_web_seed_downloads),
DEPRECATED_SET(rate_limit_utp, false, &session_impl::update_rate_limit_utp),
DEPRECATED_SET(rate_limit_utp, true, &session_impl::update_rate_limit_utp),
DEPRECATED_SET(announce_double_nat, false, nullptr),
SET(seeding_outgoing_connections, true, nullptr),
SET(no_connect_privileged_ports, false, &session_impl::update_privileged_ports),