I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Link fixes (tickets #1334, #1335)

Browse Source 
Clarify DESTINATION in SESSION STATUS in SAM v1/v2 (ticket #1334)
This commit is contained in:
zzz
2014-07-20 12:19:57 +00:00
parent 02954e30ea
commit a3a9c74dd9
4 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
i2p2www/pages/site/docs/api/sam.html
View File

@ -147,7 +147,8 @@ as to why the session could not be created.
Note that there is no warning given if the $name is not found and Note that there is no warning given if the $name is not found and
a transient destination is created instead. a transient destination is created instead.
Note that the actual transient destination is not output in the reply. Note that the actual transient base 64 destination is not output in the reply;
it is the $name or TRANSIENT as supplied in SESSION CREATE.
If you need these features, you must use <a href="samv3>SAM V3</a>. If you need these features, you must use <a href="samv3>SAM V3</a>.

3
i2p2www/pages/site/docs/api/samv2.html
View File

@ -151,7 +151,8 @@ as to why the session could not be created.
Note that there is no warning given if the $name is not found and Note that there is no warning given if the $name is not found and
a transient destination is created instead. a transient destination is created instead.
Note that the actual transient destination is not output in the reply. Note that the actual transient base 64 destination is not output in the reply;
it is the $name or TRANSIENT as supplied in SESSION CREATE.
If you need these features, you must use <a href="samv3>SAM V3</a>. If you need these features, you must use <a href="samv3>SAM V3</a>.

2
i2p2www/pages/site/docs/api/samv3.html
View File

@ -463,7 +463,7 @@ V1/V2 Compatible Datagram Handling
In SAM V3, the preferred way to send datagrams is via the datagram socket In SAM V3, the preferred way to send datagrams is via the datagram socket
at port 7655 as documented above. However, repliable datagrams may be sent at port 7655 as documented above. However, repliable datagrams may be sent
directly via the SAM bridge socket using the DATAGRAM SEND command, directly via the SAM bridge socket using the DATAGRAM SEND command,
as documented in <a href="sam>SAM V1</a> and <a href="samv2>SAM V2</a>. as documented in <a href="sam">SAM V1</a> and <a href="samv2">SAM V2</a>.
As of release 0.9.14 (version 3.1), anonymous datagrams may be sent As of release 0.9.14 (version 3.1), anonymous datagrams may be sent
directly via the SAM bridge socket using the RAW SEND command, directly via the SAM bridge socket using the RAW SEND command,

2
i2p2www/pages/site/docs/spec/datagrams.html
View File

@ -99,7 +99,7 @@ currently limit messages to about 32 KB, so the data length here is limited to a
31.5 KB. 31.5 KB.
{%- endtrans %}</li> {%- endtrans %}</li>
<li>{% trans dgrams=site_url('docs/api/datagrams') -%} <li>{% trans dgrams=site_url('docs/api/datagrams') -%}
See <a href={{ dgrams }}">important notes</a> about the reliability of large datagrams. See <a href="{{ dgrams }}">important notes</a> about the reliability of large datagrams.
For best results, limit the payload to about 10 KB or less. For best results, limit the payload to about 10 KB or less.
{%- endtrans %}</li> {%- endtrans %}</li>
<li>{% trans -%} <li>{% trans -%}