diff --git a/docs/building.html b/docs/building.html index 1bfe9fba2..1aae861bd 100644 --- a/docs/building.html +++ b/docs/building.html @@ -3,7 +3,7 @@ - + libtorrent manual diff --git a/docs/client_test.html b/docs/client_test.html index 9039b3780..9004c3c77 100644 --- a/docs/client_test.html +++ b/docs/client_test.html @@ -3,7 +3,7 @@ - + client_test example program diff --git a/docs/contributing.html b/docs/contributing.html index b772aa89c..50bf3c307 100644 --- a/docs/contributing.html +++ b/docs/contributing.html @@ -3,7 +3,7 @@ - + libtorrent manual diff --git a/docs/dht_extensions.html b/docs/dht_extensions.html index b30dabfea..e2ac67cf7 100644 --- a/docs/dht_extensions.html +++ b/docs/dht_extensions.html @@ -3,7 +3,7 @@ - + diff --git a/docs/dht_rss.html b/docs/dht_rss.html index 6b162c2b8..8e10d668a 100644 --- a/docs/dht_rss.html +++ b/docs/dht_rss.html @@ -3,7 +3,7 @@ - + BitTorrent extension for DHT RSS feeds diff --git a/docs/dht_sec.html b/docs/dht_sec.html index ce68c6075..c57801bb6 100644 --- a/docs/dht_sec.html +++ b/docs/dht_sec.html @@ -3,7 +3,7 @@ - + BitTorrent DHT security extension diff --git a/docs/dht_store.html b/docs/dht_store.html index 783ec96a4..8a301536f 100644 --- a/docs/dht_store.html +++ b/docs/dht_store.html @@ -3,7 +3,7 @@ - + BitTorrent extension for arbitrary DHT store diff --git a/docs/examples.html b/docs/examples.html index bd61ec0c0..b34057fba 100644 --- a/docs/examples.html +++ b/docs/examples.html @@ -3,7 +3,7 @@ - + libtorrent Examples diff --git a/docs/extension_protocol.html b/docs/extension_protocol.html index 11544a83e..1ebc3a258 100644 --- a/docs/extension_protocol.html +++ b/docs/extension_protocol.html @@ -3,7 +3,7 @@ - + diff --git a/docs/features.html b/docs/features.html index 32a504907..9bd7e63c3 100644 --- a/docs/features.html +++ b/docs/features.html @@ -3,7 +3,7 @@ - + libtorrent manual diff --git a/docs/gen_reference_doc.py b/docs/gen_reference_doc.py index 3ddddb4e5..02a0ecebe 100644 --- a/docs/gen_reference_doc.py +++ b/docs/gen_reference_doc.py @@ -129,9 +129,9 @@ def first_item(itr): return None def is_visible(desc): - if desc.strip() == 'hidden': return False + if desc.strip().startswith('hidden'): return False if internal: return True - if desc.strip() == 'internal': return False + if desc.strip().startswith('internal'): return False return True def highlight_signature(s): diff --git a/docs/index.html b/docs/index.html index 8fce19a27..f66e04e04 100644 --- a/docs/index.html +++ b/docs/index.html @@ -3,7 +3,7 @@ - + diff --git a/docs/libtorrent_plugins.html b/docs/libtorrent_plugins.html index e842705b5..b55f9e7b4 100644 --- a/docs/libtorrent_plugins.html +++ b/docs/libtorrent_plugins.html @@ -3,7 +3,7 @@ - + diff --git a/docs/projects.html b/docs/projects.html index 8b1b49810..5fa81309f 100644 --- a/docs/projects.html +++ b/docs/projects.html @@ -3,7 +3,7 @@ - + projects using libtorrent diff --git a/docs/python_binding.html b/docs/python_binding.html index 1c6d168db..a6da1f4c7 100644 --- a/docs/python_binding.html +++ b/docs/python_binding.html @@ -3,7 +3,7 @@ - + libtorrent python binding diff --git a/docs/todo.html b/docs/todo.html index b9b477ef7..4b7f96ad6 100644 --- a/docs/todo.html +++ b/docs/todo.html @@ -24,7 +24,7 @@ 4 important 5 relevant 15 feasible -37 notes +36 notes
relevance 4../src/session_impl.cpp:667in order to support SSL over uTP, the utp_socket manager either needs to be able to receive packets on multiple ports, or we need to peek into the first few bytes the payload stream of a socket to determine whether or not it's an SSL connection. (The former is simpler but won't do as well with NATs)
relevance 3../src/torrent.cpp:6182if peer is a really good peer, maybe we shouldn't disconnect it
relevance 2../src/torrent.cpp:8358will pick_pieces ever return an empty set?
relevance 2../src/torrent.cpp:8369will pick_pieces ever return an empty set?
relevance 1../src/torrent.cpp:1161make this depend on the error and on the filesystem the files are being downloaded to. If the error is no_space_left_on_device and the filesystem doesn't support sparse files, only zero the priorities of the pieces that are at the tails of all files, leaving everything up to the highest written piece in each file
relevance 1../src/torrent.cpp:1158make this depend on the error and on the filesystem the files are being downloaded to. If the error is no_space_left_on_device and the filesystem doesn't support sparse files, only zero the priorities of the pieces that are at the tails of all files, leaving everything up to the highest written piece in each file
relevance 1../src/torrent.cpp:5438save the send_stats state instead of throwing them away it may pose an issue when downgrading though
relevance 1../src/torrent.cpp:5444save the send_stats state instead of throwing them away it may pose an issue when downgrading though
relevance 1../src/torrent.cpp:6344should disconnect all peers that have the pieces we have not just seeds. It would be pretty expensive to check all pieces for all peers though
relevance 1../src/torrent.cpp:6350should disconnect all peers that have the pieces we have not just seeds. It would be pretty expensive to check all pieces for all peers though
relevance 0../src/bt_peer_connection.cpp:662this could be optimized using knuth morris pratt
relevance 0../src/bt_peer_connection.cpp:617this could be optimized using knuth morris pratt
relevance 0../src/bt_peer_connection.cpp:2081if we're finished, send upload_only message
relevance 0../src/bt_peer_connection.cpp:2083if we're finished, send upload_only message
relevance 0../src/bt_peer_connection.cpp:3323move the erasing into the loop above remove all payload ranges that has been sent
relevance 0../src/bt_peer_connection.cpp:3325move the erasing into the loop above remove all payload ranges that has been sent
relevance 0../src/peer_connection.cpp:5747why does this invariant not hold?
relevance 0../src/policy.cpp:857only allow _one_ connection to use this override at a time
relevance 0../src/policy.cpp:857only allow _one_ connection to use this override at a time
relevance 0../src/policy.cpp:1902how do we deal with our external address changing? Pass in a force-update maybe? and keep a version number in policy
relevance 0../src/session_impl.cpp:1943recalculate all connect candidates for all torrents
relevance 0../src/session_impl.cpp:3394have a separate list for these connections, instead of having to loop through all of them
relevance 0../src/session_impl.cpp:4484allow extensions to sort torrents for queuing
relevance 0../src/session_impl.cpp:4640use a lower limit than m_settings.connections_limit to allocate the to 10% or so of connection slots for incoming connections
relevance 0../src/session_impl.cpp:4675also take average_peers into account, to create a bias for downloading torrents with < average peers
relevance 0../src/session_impl.cpp:4674make this bias configurable
relevance 0../src/session_impl.cpp:4675also take average_peers into account, to create a bias for downloading torrents with < average peers
relevance 0../src/session_impl.cpp:4819make configurable
relevance 0../src/session_impl.cpp:4833make configurable
relevance 0../src/storage.cpp:324if the read fails, set error and exit immediately
relevance 0../src/storage.cpp:324if the read fails, set error and exit immediately
relevance 0../src/storage.cpp:358if the read fails, set error and exit immediately
relevance 0../src/storage.cpp:629make this more generic to not just work if files have been renamed, but also if they have been merged into a single file for instance maybe use the same format as .torrent files and reuse some code from torrent_info
relevance 0../src/storage.cpp:1246what if file_base is used to merge several virtual files into a single physical file? We should probably disable this if file_base is used. This is not a widely used feature though
relevance 0../src/storage.cpp:1246what if file_base is used to merge several virtual files into a single physical file? We should probably disable this if file_base is used. This is not a widely used feature though
relevance 0../src/torrent.cpp:1362is verify_peer_cert called once per certificate in the chain, and this function just tells us which depth we're at right now? If so, the comment makes sense. any certificate that isn't the leaf (i.e. the one presented by the peer) should be accepted automatically, given preverified is true. The leaf certificate need to be verified to make sure its DN matches the info-hash
relevance 0../src/torrent.cpp:1359is verify_peer_cert called once per certificate in the chain, and this function just tells us which depth we're at right now? If so, the comment makes sense. any certificate that isn't the leaf (i.e. the one presented by the peer) should be accepted automatically, given preverified is true. The leaf certificate need to be verified to make sure its DN matches the info-hash
relevance 0../src/torrent.cpp:5171make this more generic to not just work if files have been renamed, but also if they have been merged into a single file for instance maybe use the same format as .torrent files and reuse some code from torrent_info The mapped_files needs to be read both in the network thread and in the disk thread, since they both have their own mapped files structures which are kept in sync
relevance 0../src/torrent.cpp:5177make this more generic to not just work if files have been renamed, but also if they have been merged into a single file for instance maybe use the same format as .torrent files and reuse some code from torrent_info The mapped_files needs to be read both in the network thread and in the disk thread, since they both have their own mapped files structures which are kept in sync
relevance 0../src/torrent.cpp:5313if this is a merkle torrent and we can't restore the tree, we need to wipe all the bits in the have array, but not necessarily we might want to do a full check to see if we have all the pieces. This is low priority since almost no one uses merkle torrents
relevance 0../src/torrent.cpp:5495make this more generic to not just work if files have been renamed, but also if they have been merged into a single file for instance. using file_base
relevance 0../src/torrent.cpp:5501make this more generic to not just work if files have been renamed, but also if they have been merged into a single file for instance. using file_base
relevance 0../src/torrent.cpp:8048go through the pieces we have and count the total number of downloaders we have. Only count peers that are interested in us since some peers might not send have messages for pieces we have it num_interested == 0, we need to pick a new piece
relevance 0../src/udp_tracker_connection.cpp:550it would be more efficient to not use a string here. however, the problem is that some trackers will respond with actual strings. For example i2p trackers
relevance 0../src/udp_tracker_connection.cpp:550it would be more efficient to not use a string here. however, the problem is that some trackers will respond with actual strings. For example i2p trackers
relevance 0../src/utp_stream.cpp:1573this loop may not be very efficient
relevance 0../src/utp_stream.cpp:1573this loop may not be very efficient
relevance 0../src/kademlia/routing_table.cpp:280instad of refreshing a bucket by using find_nodes, ping each node periodically
relevance 0../src/kademlia/routing_table.cpp:280instad of refreshing a bucket by using find_nodes, ping each node periodically
relevance 0../include/libtorrent/config.hpp:305Make this count Unicode characters instead of bytes on windows
relevance 0../include/libtorrent/config.hpp:305Make this count Unicode characters instead of bytes on windows
relevance 0../include/libtorrent/proxy_base.hpp:166it would be nice to remember the bind port and bind once we know where the proxy is m_sock.bind(endpoint, ec);
relevance 0../include/libtorrent/proxy_base.hpp:166it would be nice to remember the bind port and bind once we know where the proxy is m_sock.bind(endpoint, ec);
relevance 0../include/libtorrent/torrent_info.hpp:123include the number of peers received from this tracker, at last announce
relevance 0../include/libtorrent/torrent_info.hpp:123include the number of peers received from this tracker, at last announce
relevance 0../include/libtorrent/upnp.hpp:121support using the windows API for UPnP operations as well
relevance 0../include/libtorrent/upnp.hpp:121support using the windows API for UPnP operations as well