Returns the storage implementation for this torrent. This depends on the storage contructor function that was passed to session::add_torrent.
+++bool super_seeding() const; +void super_seeding(bool on) const; ++
Enables or disabled super seeding/initial seeding for this torrent. The torrent +needs to be a seed for this to take effect. The overload that returns a bool +tells you of super seeding is enabled or not.
+
+
+enum flags_t { overwrite_existing = 1 };
+void add_piece(int piece, char const* data, int flags = 0) const;
+
+
+This function will write data to the storage as piece piece, as if it had +been downloaded from a peer. data is expected to point to a buffer of as many +bytes as the size of the specified piece. The data in the buffer is copied and +passed on to the disk IO thread to be written at a later point.
+By default, data that's already been downloaded is not overwritten by this buffer. If +you trust this data to be correct (and pass the piece hash check) you may pass the +overwrite_existing flag. This will instruct libtorrent to overwrite any data that +may already have been downloaded with this data.
+Since the data is written asynchronously, you may know that is passed or failed the +hash check by waiting for piece_finished_alert or has_failed_alert.
+@@ -3132,6 +3171,8 @@ struct session_settings bool rate_limit_ip_overhead; bool announce_to_all_trackers; + bool prefer_udp_trackers; + bool strict_super_seeding; };user_agent this is the client identification to the tracker. @@ -3364,6 +3405,14 @@ in tier 1 are announced as well. This is the uTorrent behavior. If it's set to false, the behavior is as defined by the multi tracker specification. It defaults to false, which is the same behavior previous versions of libtorrent has had as well.
+prefer_udp_trackers is true by default. It means that trackers may +be rearranged in a way that udp trackers are always tried before http +trackers for the same hostname. Setting this to fails means that the +trackers' tier is respected and there's no preference of one protocol +over another.
+strict_super_seeding when this is set to true, a piece has to +have been forwarded to a third peer before another one is handed out. +This is the traditional definition of super seeding.