IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2023/10/22
@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+dr|z3d
+hagen
+hk
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+weko
+wodencafe
AHON1
Arch
BubbRubb
C341
Daddy
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest46813
Irc2PGuest57893
Irc2PGuest61215
Irc2PGuest62061
Irc2PGuest82088
Leopold
Onn4l7h
Onn4|7h
SigSegv
Sleepy
SlippyJoe_
T3s|4_
Teeed
aargh
acetone_
ardu
b3t4f4c3__
bak83_
carried6590
cumlord
dr4wd3
eyedeekay_bnc
idontpee
ohThuku1
poriori
profetikla
r00tobo_BNC
rapidash
solidx66
thetia
u5657
uop23ip
w8rabbit
wew
x74a6
robin SAM3.1 can only have one STREAM ACCEPT pending at a time. But can it have multiple _active_ stream connections?
zzz no, both are unlimited
robin Spec says there is an ALREADY_ACCEPTING error in 3.1
zzz spec says:
zzz 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.
zzz but I think that's wrong, I think it was fixed in the 3.2 timeframe but was fixed for 3.1 as well
zzz try it and let me know
robin Ok, for now I will comment out the code that would have detected the condition and see what happens.
robin When the time comes I will need 3.1 and 3.2 routers to test against.
robin I suppose I cna build those from sources by fetching appropriate tags
zzz no need, just set the appropriate min/max
zzz I think I probably put that line in because we were waiting for i2pd to support it; not sure if they ever did, you'd have to ask orignal
robin So if I say HELLO VERSION MAX=3.1 then even a modern router will 'degrade' its functionality?
zzz yes
zzz that's the whole point of min/max
robin Ah, OK. Much easier
zzz I peaked at our code and I'm about 99% sure we support concurrent accepts. I peaked at i2pd's code and I'm about 80% sure they don't.
robin All I can detect is the SAM version number, not which implementation it is. But I will get the ALREADY_ACCEPTING error anyway
zzz yeah, java offers some 3.2/3.3 "bonus features" for 3.1 like that, no reason not to really
zzz I'll add a note to the spec
robin As long as i2pd advertises being SAM v3.1 it should all work
zzz right
zzz so that's why the spec says what it does