wornvirtue
/
premiere-libtorrent
forked from premiere/premiere-libtorrent
1
0
Fork 0
Code Pull Requests Activity

updated feature list and corrected the threads section in the main docs

This commit is contained in:
Arvid Norberg 2008-12-21 02:19:02 +00:00
parent 24668058fc
commit 325f9babe8
2 changed files with 17 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/features.rst
View File

@ -33,12 +33,19 @@ following features:
some `DHT extensions`_.
* support for IPv6
* NAT-PMP and UPnP support (automatic port mapping on routers that supports it)
* piece-wise, unordered, incremental file allocation
* uses separate threads for checking files and for main downloader, with a
fool-proof thread-safe library interface. (i.e. There's no way for the
user to cause a deadlock). (see threads_)
* uses a separate disk I/O thread to not have the disk ever block on network or
client interaction. (see threads_).
* supports the bittorrent `extension protocol`_. See extensions_.
* supports the uTorrent metadata transfer protocol (i.e. magnet links).
* supports the uTorrent peer exchange protocol (PEX).
* supports local peer discovery (multicasts for peers on the same local network)
* adjusts the length of the request queue depending on download rate.
* multitracker extension support (as `specified by John Hoffman`__)
* has an adjustable read and write disk cache for improved disk throughput.
* multitracker extension support (supports both the `specification by John Hoffman`__
and the uTorrent interpretation).
* tracker scrapes
* supports both sparse files and compact file allocation (where pieces
are kept consolidated on disk)
* supports files > 2 gigabytes.
* serves multiple torrents on a single port and in a single thread
* fast resume support, a way to get rid of the costly piece check at the
@ -58,7 +65,6 @@ following features:
* implements fair trade. User settable trade-ratio, must at least be 1:1,
but one can choose to trade 1 for 2 or any other ratio that isn't unfair
to the other party.
* supports an `extension protocol`_. See extensions_.
* supports the ``no_peer_id=1`` extension that will ease the load off trackers.
* possibility to limit the number of connections.
* delays have messages if there's no other outgoing traffic to the peer, and

13
docs/manual.rst
View File

@ -5278,15 +5278,12 @@ libtorrent starts 2 or 3 threads.
idle in a ``select()`` call most of the time. This thread runs the main loop
that will send and receive data on all connections.
* The second thread is a hash-check thread. Whenever a torrent is added it will
first be passed to this thread for checking the files that may already have been
downloaded. If there is any resume data this thread will make sure it is valid
and matches the files. Once the torrent has been checked, it is passed on to the
main thread that will start it. The hash-check thread has a queue of torrents,
it will only check one torrent at a time.
* The second thread is the disk I/O thread. All disk read and write operations
are passed to this thread and messages are passed back to the main thread when
the operation compeltes. The disk thread also verifies the piece hashes.
* The third thread is spawned by asio on systems that don't support
non-blocking host name resolution to simulate non-blocking behavior.
* The third and forth threads are spawned by asio on systems that don't support
non-blocking host name resolution to simulate non-blocking getaddrinfo().
storage allocation