|
@@ -642,14 +642,19 @@ aria2c -o myfile.zip http://mirror1/file.zip http://mirror2/file.zip</td>
|
|
|
</dt>
|
|
|
<dd>
|
|
|
<p>
|
|
|
- Specify URI selection algorithm. Possible values are <em>inorder</em> and
|
|
|
- <em>feedback</em>. If <em>inorder</em> is given, URI is tried in the order
|
|
|
- appeared in the URI list. If <em>feedback</em> is given, aria2 uses
|
|
|
- download speed observed in the previous downloads and choose fastest
|
|
|
- server in the URI list. This also effectively skips dead
|
|
|
+ Specify URI selection algorithm. Possible values are <em>inorder</em>,
|
|
|
+ <em>feedback</em> and <em>adaptive</em>. If <em>inorder</em> is given, URI is tried in
|
|
|
+ the order appeared in the URI list. If <em>feedback</em> is given, aria2
|
|
|
+ uses download speed observed in the previous downloads and choose
|
|
|
+ fastest server in the URI list. This also effectively skips dead
|
|
|
mirrors. The observed download speed is a part of performance
|
|
|
profile of servers mentioned in <strong>--server-stat-of</strong> and
|
|
|
- <strong>--server-stat-if</strong> options.
|
|
|
+ <strong>--server-stat-if</strong> options. If <em>adaptive</em> is given, selects one of
|
|
|
+ the best mirrors for the first and reserved connections. For
|
|
|
+ supplementary ones, it returns mirrors which has not been tested
|
|
|
+ yet, and if each of them has already been tested, returns mirrors
|
|
|
+ which has to be tested again. Otherwise, it doesn't select anymore
|
|
|
+ mirrors. Like <em>feedback</em>, it uses a performance profile of servers.
|
|
|
Default: <em>inorder</em>
|
|
|
</p>
|
|
|
</dd>
|
|
@@ -2174,7 +2179,7 @@ files in the program, then also delete it here.</p></div>
|
|
|
</div>
|
|
|
<div id="footer">
|
|
|
<div id="footer-text">
|
|
|
-Last updated 2009-01-19 22:58:36 JST
|
|
|
+Last updated 2009-01-19 23:13:30 JST
|
|
|
</div>
|
|
|
</div>
|
|
|
</body>
|