streaming clarification

This commit is contained in:
zzz
2020-05-06 11:59:30 +00:00
parent 874681edb8
commit 54b5f4c5ea
2 changed files with 10 additions and 6 deletions

View File

@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Streaming Library{% endtrans %}{% endblock %}
{% block lastupdated %}{% trans %}July 2018{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.36{% endblock %}
{% block lastupdated %}2020-04{% endblock %}
{% block accuratefor %}0.9.46{% endblock %}
{% block content %}
<h2>{% trans %}Overview{% endtrans %}</h2>
@ -300,7 +300,8 @@ As of release {{ release }}.
{%- endtrans %}</td></tr>
<tr><td>i2p.streaming.maxMessageSize</td><td>1730</td><td>{% trans -%}
The MTU in bytes.
The maximum size of the payload,
i.e. the MTU in bytes.
{%- endtrans %}</td></tr>
<tr><td>i2p.streaming.maxResends</td><td>8</td><td>{% trans -%}
@ -403,7 +404,10 @@ a large amount of overhead.
The MTU is specified by the option i2p.streaming.maxMessageSize.
The current default MTU of 1730 was chosen to fit precisely into two 1K I2NP tunnel messages,
including overhead for the typical case.
{%- endtrans %}</p>
{%- endtrans %}
Note: This is the maximum size of the payload only, not including the header.
</p>
<p>{% trans -%}
The first message in a connection includes a 387 byte (typical) Destination added by the streaming layer,