Section headers, update info on large leasesets

This commit is contained in:
zzz
2014-01-28 15:24:44 +00:00
parent fd87732164
commit 2d49dc8aee

View File

@@ -89,6 +89,7 @@ The client may now initiate or receive connections from other I2P destinations.
{%- endtrans %}</p> {%- endtrans %}</p>
<h2 id="options">{% trans %}I2CP Options{% endtrans %}</h2> <h2 id="options">{% trans %}I2CP Options{% endtrans %}</h2>
<h3>{% trans %}Router-side Options{% endtrans %}</h3>
<p>{% trans i2cp=site_url('docs/spec/i2cp') -%} <p>{% trans i2cp=site_url('docs/spec/i2cp') -%}
The following options are traditionally passed to the router via The following options are traditionally passed to the router via
a <a href="{{ i2cp }}#struct_SessionConfig">SessionConfig</a> contained in a <a href="{{ i2cp }}#msg_CreateSession">CreateSession Message</a> or a <a href="{{ i2cp }}#msg_ReconfigureSession">ReconfigureSession Message</a>. a <a href="{{ i2cp }}#struct_SessionConfig">SessionConfig</a> contained in a <a href="{{ i2cp }}#msg_CreateSession">CreateSession Message</a> or a <a href="{{ i2cp }}#msg_ReconfigureSession">ReconfigureSession Message</a>.
@@ -344,8 +345,8 @@ Higher is higher priority.
<td>2</td> <td>2</td>
<td>{% trans -%} <td>{% trans -%}
Number of tunnels in. Number of tunnels in.
Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are not Limit was increased from 6 to 16 in release 0.9; however, numbers higher than 6 are
currently recommended, as this is untested and is incompatible with older releases. incompatible with older releases.
{%- endtrans %}</td> {%- endtrans %}</td>
</tr> </tr>
@@ -430,6 +431,7 @@ Since options are encoded in a <a href="{{ commonstructures }}#type_Mapping">Map
all option names and values are limited to 255 bytes (not characters) maximum. all option names and values are limited to 255 bytes (not characters) maximum.
{%- endtrans %}</p> {%- endtrans %}</p>
<h3>{% trans %}Client-side Options{% endtrans %}</h3>
<p>{% trans -%} <p>{% trans -%}
The following options are interpreted on the client side, The following options are interpreted on the client side,
and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call. and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call.