a845afe6d9
fix warnings
2019-04-10 08:05:36 +02:00
8b067310b1
merged RC_1_1 into master
2019-01-12 00:53:45 +01:00
b443d33430
bump version number
2019-01-11 11:30:37 +01:00
786d78b6c9
only allow cwnd to be reduced so often
2019-01-11 02:15:11 +01:00
0413ee581a
added more TORRENT_DEPRECATED_ENUM and deprecated unused aio_max in settings_pack
2018-12-10 11:45:44 +01:00
8f54146555
take a string_view in setting_by_name
2018-12-04 19:05:31 +01:00
6381b35891
bump verson to 1.1.11.0
2018-11-16 15:52:16 +01:00
200bb494c3
bump version
2018-10-01 09:41:37 +02:00
78a344bd8b
merged RC_1_1 into master
2018-09-05 08:25:14 -07:00
214ace3efe
raise default value for active_limit to 500, since it's supposed to be an upper sanity check limit
2018-09-02 19:25:06 +02:00
55215742af
merged RC_1_1 into master
2018-08-25 14:13:51 +02:00
b90564d418
remove the IPv6 enable/disable build config
2018-08-19 22:20:54 +02:00
6620b6e774
dial back the connect boost a bit from recent update
2018-08-13 19:17:01 +02:00
b3dbce5790
merge RC_1_1 into master
2018-08-13 09:32:17 +02:00
6d2541f131
improve connect-boost feature, to make new torrents quickly connect peers
2018-08-09 20:12:56 +02:00
51fb1e3d6b
tweak the auto-cache-size logic to have slightly smaller cache
2018-08-06 14:06:32 +02:00
6caddf6b8e
fix deprecation of mmap_cache
2018-08-03 12:51:04 +02:00
2f56fa6c3e
bump version to 1.1.9
2018-07-20 13:06:12 +02:00
1ebc5f9ef2
remove special handling of uTP peers
2018-07-20 07:47:08 +02:00
b750b6cc2c
deprecate (and disable) the force-proxy setting. Instead, always use the proxy when set, never fall back on circumventing it
2018-07-08 18:26:47 +02:00
4576723090
bump version to 1.1.8
2018-06-25 12:25:11 +02:00
b67166b29d
merged RC_1_1 into master
2018-06-24 17:59:28 +02:00
56a25ce280
bump checking_mem_usage default setting
2018-06-24 07:44:58 +02:00
b0b1bfb7a9
enable coalesce_reads and coalesce_writes by default on windows
2018-06-24 07:39:59 +02:00
b26467c04e
deprecate network-threads setting
2018-06-10 19:34:07 +02:00
fe612ca167
replace the TORRENT_CFG ABI check with inline namespaces around the symbol that can change ABI based on build configuration options
2018-05-13 19:25:17 +02:00
f0227451a6
merged RC_1_1 into master
2018-04-13 01:47:41 +02:00
aaf9304a3b
update year in copyright header
2018-04-09 09:04:33 +02:00
105934e578
bump version
2018-04-08 23:08:39 +02:00
9df4d4b7f8
replace typedef with using. replace NULL with nullptr. cleanup page_aligned_allocator
2018-03-23 11:19:46 +01:00
9696082355
merged RC_1_1 into master
2018-02-25 09:36:12 +01:00
1ede34da8a
undo the patch to restore incoming TCP connections over SOCKS5
2018-02-19 00:01:42 +01:00
308cbfe097
merged RC_1_1 into master
2018-01-27 02:36:55 +01:00
bc4d53c71f
restore support for incoming connections over SOCKS5 (disabled by default)
2018-01-25 09:14:14 +01:00
4fef787212
merged RC_1_1 into master
2018-01-24 00:37:05 +01:00
efd096d879
use unique peer_ids per connection
2018-01-23 16:40:16 +01:00
c8bf782bd0
bump version number to 1.1.6
2017-12-29 15:53:51 +01:00
0848d9b7f5
change defaults for rate_limit_utp setting
2017-12-17 08:50:25 +01:00
c16eb32b94
merge RC_1_1 into master
2017-12-03 18:12:35 +01:00
4b467f82ac
fix issue with initializing settings on session construction
2017-12-02 12:20:36 +01:00
5480c08184
enable/disable the internal ip notifier with new setting ( #2487 )
2017-11-01 10:51:51 +01:00
c66f4cc62a
fix some warnings, mostly 0 -> nullptr
2017-09-28 07:33:10 -07:00
0232dc35cd
deprecate lock_files ( #2344 )
...
File locking interacts poorly with the path to replace a read only file handle
with a read/write one. For performance reasons the old handle is not closed
until the new one is put in place. With file locking this obviously cannot
work because the first handle is holding a lock on the file. As a result,
file_pool::open_file fails in this case. Even if we dropped the reference to
the read only file handle before attempting to re-open it, the open could still
fail if another thread is holding a reference to the read only handle.
There doesn't seem to be a good way around this. The simple solution would be
to always open files in read/write mode, but that has obvious safety downsides.
Any other solution would significantly complicate the file pool code.
Deprecating file locking seems to be the least bad option.
2017-09-17 10:43:27 +02:00
bb51dcdbb9
move dht_settings into its own header cpp file-pair and dht_settings into the dht namespace
2017-09-04 22:38:16 +02:00
061732ddec
bump version
2017-09-04 15:35:45 +02:00
f311bf354e
remove left-overs from disk buffer pool allocator
2017-08-21 16:36:00 +02:00
2365611507
remove support for using a pool allocator for disk buffers ( #2257 )
2017-08-19 11:04:39 +02:00
73e898e38e
disable disk cache pool allocator by default
...
The pool allocator has known issues with not releasing memory when it should
and is of dubious benefit.
See #2251
2017-08-18 09:39:24 +02:00
b38efb6c65
make alert category flags be a strong type
2017-07-26 07:20:47 -07:00
5188c190db
bump version number
2017-07-02 15:03:46 -04:00
arvidn