regenerated html

This commit is contained in:
Arvid Norberg 2010-03-20 08:26:44 +00:00
parent b2484ead10
commit 0e7976675b
1 changed files with 25 additions and 2 deletions

View File

@ -264,7 +264,12 @@ make sure this requirement is fulfilled.</p>
<pre class="literal-block"> <pre class="literal-block">
struct create_torrent struct create_torrent
{ {
enum { optimize = 1, merkle = 2 }; enum {
optimize = 1
, merkle = 2
, modification_time = 4
, symlink = 8
};
create_torrent(file_storage&amp; fs, int piece_size = 0, int pad_size_limit = -1, int flags = optimize); create_torrent(file_storage&amp; fs, int piece_size = 0, int pad_size_limit = -1, int flags = optimize);
create_torrent(torrent_info const&amp; ti); create_torrent(torrent_info const&amp; ti);
@ -290,7 +295,12 @@ struct create_torrent
<h2>create_torrent()</h2> <h2>create_torrent()</h2>
<blockquote> <blockquote>
<pre class="literal-block"> <pre class="literal-block">
enum { optimize = 1, merkle = 2 }; enum {
optimize = 1
, merkle = 2
, modification_time = 4
, symlink = 8
};
create_torrent(file_storage&amp; fs, int piece_size = 0, int pad_size_limit = -1, int flags = optimize); create_torrent(file_storage&amp; fs, int piece_size = 0, int pad_size_limit = -1, int flags = optimize);
create_torrent(torrent_info const&amp; ti); create_torrent(torrent_info const&amp; ti);
</pre> </pre>
@ -320,6 +330,19 @@ be opened in clients that don't specifically support merkle torrents.
The benefit is that the resulting torrent file will be much smaller and The benefit is that the resulting torrent file will be much smaller and
not grow with more pieces. When this option is specified, it is not grow with more pieces. When this option is specified, it is
recommended to have a fairly small piece size, say 64 kiB.</dd> recommended to have a fairly small piece size, say 64 kiB.</dd>
<dt>modification_time</dt>
<dd>This will include the file modification time as part of the torrent.
This is not enabled by default, as it might cause problems when you
create a torrent from separate files with the same content, hoping to
yield the same info-hash. If the files have different modification times,
with this option enabled, you would get different info-hashes for the
files.</dd>
<dt>symlink</dt>
<dd>If this flag is defined, files that are symlinks get a symlink attribute
set on them. The file data will still be the same, the symlink will always
be followed when opening the file, but the file list will include the path
of the symlink so that the original directory structure can be reproduced
on the downloading side.</dd>
</dl> </dl>
</div> </div>
<div class="section" id="generate"> <div class="section" id="generate">