diff --git a/docs/manual.html b/docs/manual.html index 4c0dc5cf1..997469eb3 100644 --- a/docs/manual.html +++ b/docs/manual.html @@ -360,7 +360,7 @@ the session, it conta

  • start DHT, LSD, UPnP, NAT-PMP etc (see start_dht() stop_dht() set_dht_settings() dht_state() is_dht_running() start_lsd() stop_lsd(), start_upnp() stop_upnp() and start_natpmp() stop_natpmp())

    • -

  • parse .torrent-files and add them to the session (see bdecode() bencode() and `add_torrent()`_)

    +

  • parse .torrent-files and add them to the session (see bdecode() bencode() and async_add_torrent() add_torrent())

  • main loop (see session)

    @@ -1414,7 +1414,7 @@ minutes between refreshes.

    This object is used as a template for adding torrents from feeds, but some torrent specific fields will be overridden by the individual torrent being added. For more information on the -add_torrent_params, see `add_torrent()`_.

    +add_torrent_params, see async_add_torrent() add_torrent().

    The returned feed_handle is a handle which is used to interact with the feed, things like forcing a refresh or querying for information about the items in the feed. For more information, @@ -2635,7 +2635,7 @@ and no calculation is required.

    boost::filesystem::path save_path() const;
    -

    save_path() returns the path that was given to `add_torrent()`_ when this torrent +

    save_path() returns the path that was given to async_add_torrent() add_torrent() when this torrent was started.

    @@ -4711,7 +4711,7 @@ are kept in memory after the torrent becomes a seed or not. If it is set to needed anymore since the torrent won't download anything more). If it's set to false they are not freed. If they are freed, the torrent_info returned by get_torrent_info() will return an object that may be incomplete, that -cannot be passed back to `add_torrent()`_ for instance.

    +cannot be passed back to async_add_torrent() add_torrent() for instance.

    upnp_ignore_nonrouters indicates whether or not the UPnP implementation should ignore any broadcast response from a device whose address is not the configured router for this machine. i.e. it's a way to not talk to other @@ -5855,7 +5855,7 @@ torrent_handle add_magnet_uri(session& ses, std::string const& uri and adds the torrent to the specified session (ses). It returns the handle to the newly added torrent, or an invalid handle in case parsing failed. To control some initial settings of the torrent, sepcify those in -the add_torrent_params, p. See `add_torrent()`_.

    +the add_torrent_params, p. See async_add_torrent() add_torrent().

    The overload that does not take an error_code throws an exception on error and is not available when building without exception support.

    A simpler way to add a magnet link to a session is to pass in the @@ -8416,7 +8416,7 @@ torrents are being downloaded at any given time, and once a torrent is completel downloaded, the next in line is started.

    Torrents that are auto managed are subject to the queuing and the active torrents limits. To make a torrent auto managed, set auto_managed to true when adding the -torrent (see `add_torrent()`_).

    +torrent (see async_add_torrent() add_torrent()).

    The limits of the number of downloading and seeding torrents are controlled via active_downloads, active_seeds and active_limit in session_settings. These limits takes non auto managed torrents into account as well. If there are @@ -8464,7 +8464,7 @@ will not check the piece hashes then, and rely on the information given in the fast-resume data. The fast-resume data also contains information about which blocks, in the unfinished pieces, were downloaded, so it will not have to start from scratch on the partially downloaded pieces.

    -

    To use the fast-resume data you simply give it to `add_torrent()`_, and it +

    To use the fast-resume data you simply give it to async_add_torrent() add_torrent(), and it will skip the time consuming checks. It may have to do the checking anyway, if the fast-resume data is corrupt or doesn't fit the storage for that torrent, then it will not trust the fast-resume data and just do the checking.

    @@ -8702,7 +8702,7 @@ to where they belong. This is the recommended (and default) mode.
    • Support for this is deprecated and will be removed in future versions of libtorrent. It's still described in here for completeness.

    The allocation mode is selected when a torrent is started. It is passed as an -argument to session::add_torrent() (see `add_torrent()`_).

    +argument to session::add_torrent() (see async_add_torrent() add_torrent()).

    The decision to use full allocation or compact allocation typically depends on whether any files have priority 0 and if the filesystem supports sparse files.

    @@ -9118,33 +9118,6 @@ altogether. You can use:

    boost::filesystem::path::default_name_check(boost::filesystem::native);

    for example. For more information, see the Boost.Filesystem docs.

    -
    -
    -

    Docutils System Messages

    -
    -

    System Message: ERROR/3 (manual.rst, line 25); backlink

    -Unknown target name: "add_torrent()".
    -
    -

    System Message: ERROR/3 (manual.rst, line 1189); backlink

    -Unknown target name: "add_torrent()".
    -
    -

    System Message: ERROR/3 (manual.rst, line 2538); backlink

    -Unknown target name: "add_torrent()".
    -
    -

    System Message: ERROR/3 (manual.rst, line 4741); backlink

    -Unknown target name: "add_torrent()".
    -
    -

    System Message: ERROR/3 (manual.rst, line 6054); backlink

    -Unknown target name: "add_torrent()".
    -
    -

    System Message: ERROR/3 (manual.rst, line 8445); backlink

    -Unknown target name: "add_torrent()".
    -
    -

    System Message: ERROR/3 (manual.rst, line 8508); backlink

    -Unknown target name: "add_torrent()".
    -
    -

    System Message: ERROR/3 (manual.rst, line 8703); backlink

    -Unknown target name: "add_torrent()".