From 7fec0b308f96121a84ee8969b850a26f3da9ae71 Mon Sep 17 00:00:00 2001
From: zzz <zzz@i2pmail.org>
Date: Fri, 17 Nov 2023 15:04:09 -0500
Subject: [PATCH] SAM: Add note about i2pd concurrent accepts
---
i2p2www/pages/site/docs/api/samv3.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/i2p2www/pages/site/docs/api/samv3.html b/i2p2www/pages/site/docs/api/samv3.html
index a404607e7..d8641cf30 100644
--- a/i2p2www/pages/site/docs/api/samv3.html
+++ b/i2p2www/pages/site/docs/api/samv3.html
@@ -1,6 +1,6 @@
{% extends "global/layout.html" %}
{% block title %}SAM V3{% endblock %}
-{% block lastupdated %}2023-10{% endblock %}
+{% block lastupdated %}2023-11{% endblock %}
{% block accuratefor %}API 0.9.59{% endblock %}
{% block content %}
<p>SAM is a simple client protocol for interacting with I2P.
@@ -920,7 +920,7 @@ As of SAM 3.2,
multiple concurrent pending STREAM ACCEPTs are allowed on the same session ID (even with the same port).
Prior to 3.2, concurrent accepts would fail with ALREADY_ACCEPTING.
Note: Java I2P also supports concurrent ACCEPTs on SAM 3.1, as of release 0.9.24 (2016-01).
-i2pd does not support concurrent ACCEPTs on SAM 3.1.
+i2pd also supports concurrent ACCEPTs on SAM 3.1, as of release 2.50.0 (2023-12).
</p>
<h4>Accept Response</h4>
--
GitLab