kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SAMv3 minor updates

Browse Source
This commit is contained in:
zzz
2020-11-21 10:21:40 -05:00
parent a79864350f
commit 8d0e38392e
1 changed files with 17 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,14 +1,23 @@
{% extends "global/layout.html" %}
{% block title %}SAM V3{% endblock %}
{% block lastupdated %}2020-10{% endblock %}
{% block lastupdated %}2020-11{% endblock %}
{% block accuratefor %}0.9.48{% endblock %}
{% block content %}
<p>Specified below is a simple client protocol for interacting with I2P.
<p>SAM is a simple client protocol for interacting with I2P.
SAM is the recommended protocol for non-Java applications to connect to the I2P network,
and is supported by multiple router implementations.
Java applications should use the streaming or I2CP APIs directly.
</p>
<p>SAM version 3
was introduced in I2P release 0.7.3.
was introduced in I2P release 0.7.3 (May 2009) and is a stable and supported interface.
3.1 is also stable and supports the signature type option, which is strongly recommended.
More recent 3.x versions support advanced features.
</p><p>
Alternatives:
<a href="{{ site_url('docs/api/bob') }}">BOB(unsupported)</a>.
<a href="socks">SOCKS</a>,
<a href="streaming">Streaming</a>,
<a href="{{ site_url('docs/protocol/i2cp') }}">I2CP</a>,
<a href="{{ site_url('docs/api/bob') }}">BOB (deprecated)</a>.
Older versions:
<a href="{{ site_url('docs/api/sam') }}">SAM V1</a>,
<a href="{{ site_url('docs/api/samv2') }}">SAM V2</a>,
@@ -107,7 +116,7 @@ Older versions:
<td>yes</td>
<td>yes</td>
<td>yes</td>
<td><a href="https://github.com/i2p/libsam3">github.com/i2p/libsam3</a></td>
<td><a href="https://github.com/i2p/libsam3">github.com/i2p/libsam3</a><br>(Maintained by the I2P project)</td>
</tr>
<tr class="odd">
<td>mooni2p</td>
@@ -187,7 +196,7 @@ can forward back I2P datagrams to the client's datagram server.
<h3>Version 3.1 Changes</h3>
<p>
Version 3.1 was introduced in I2P release 0.9.14. SAM 3.1 is the recommended
Version 3.1 was introduced in I2P release 0.9.14 (July 2014). SAM 3.1 is the recommended
minimum SAM implementation because of its support for better signature types
than SAM 3.0.
<ul>
@@ -200,7 +209,7 @@ than SAM 3.0.
<h3>Version 3.2 Changes</h3>
<p>
Version 3.2 was introduced in I2P release 0.9.24.
Version 3.2 was introduced in I2P release 0.9.24 (January 2016).
</p>
<h4>I2CP Port and Protocol Support</h4>
@@ -248,7 +257,7 @@ Version 3.2 was introduced in I2P release 0.9.24.
<h3>Version 3.3 Changes</h3>
<p>
Version 3.3 was introduced in I2P release 0.9.25.
Version 3.3 was introduced in I2P release 0.9.25 (March 2016).
<ul>
<li>The same session may be used for streams, datagrams, and raw simultaneously.
Incoming packets and streams will be routed based on I2P protocol and to-port.