v3.0.3-beta-0003

General

• Fetching hash layers for BitTorrent V2 torrents should complete more reliably after two causes of slowdowns were resolved.
• For hybrid V1/V2 torrents, the engine now creates BitTorrent V1 connections by default and upgrades either incoming or outgoing requests if the handshake indicates support for BitTorrent V2.
• There's a new parameter in EngineSettings which controls how to create new files (preallocate them, or use sparse files).
• If a torrent is hash checked, the engine will never create any missing zero length files, nor will it truncate any files which are too long. These actions will now be created when TorrentManager.StartAsync is invoked, which is a clear signal that write operations are intended to be executed. In addition, capability works in tandem with selectively marking files with Priority.DoNotDownload. Where possible, the engine will not create files on disk when they are marked 'DoNotDownload'. This works best with BitTorrent V2, or files created using BEP47 padding files.

What's Changed

• Ensure pending messages are processed from the send queue regularly by @alanmcgovern in #673
• [dht] Allow bootstrapping from additional bootstrap routers by @alanmcgovern in #670
• Disambiguate between v1 and v2 connections more clearly by @alanmcgovern in #675
• Ensure hash checking a file is a purely read-only operation by @alanmcgovern in #674

Full Changelog: release-v3.0.2...release-v3.0.3-beta-0003