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

SAM link fix take 99

Browse Source
This commit is contained in:
zzz
2014-09-26 15:56:57 +00:00
parent 0e21289028
commit 2e301ffbe9
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}SAM V1 Specification{% endblock %}
{% block lastupdated %}July 2014{% endblock %}
{% block accuratefor %}0.9.14{% endblock %}
{% block lastupdated %}September 2014{% endblock %}
{% block accuratefor %}0.9.15{% endblock %}
{% block content %}
<p>Specified below is version 1 of a simple client protocol for interacting with
I2P.
@ -109,14 +109,14 @@ that name, it creates a new one. If the destination is specified
as TRANSIENT, it always creates a new one.
Note that DESTINATION is an identifier, <i>not</i> Base 64 encoded data.
To specify the Destination, you must use <a href="samv3>SAM V3</a>.
To specify the Destination, you must use <a href="samv3">SAM V3</a>.
The DIRECTION can be specified for STREAM sessions, instructing
The DIRECTION can be specified for STREAM sessions only, instructing
the bridge that the client will either be creating or receiving
streams, or both. If this is not specified, BOTH will be assumed.
Attempting to create an outbound stream when DIRECTION=RECEIVE
should result in an error, and incoming streams when
DIRECTION=CREATE should be ignored.
DIRECTION=CREATE will be ignored.
Additional options given should be fed into the I2P session
configuration if not interpreted by the SAM bridge (e.g.