@Xeha
@orignal
Arch2
BubbRubb
Dann
Irc2PGuest18689
Irc2PGuest20149
Irc2PGuest57895
Irc2PGuest74254
Meow
Over1
R4SAS
RN
SlippyJoe
StormyCloud
Stormycl1
Strykar
acetone_
b3t4f4c3__
duanin2
eyedeekay
gelleger1
halloy13412
itsAMe_
mareki2p
matean
n1_
ntty
poriori
qend-irc2p
r00tobo[2]
r00tobo_BNC
rapidash
semantica
shiver_
thetia
u5657
x74a6
SlippyJoe
i've been absent, sorry. re posting previous question
SlippyJoe
is there any downside to having multiple torrent clients use the same sam bridge instance ? libtorrent has config options for SAM session quantity of I2P inbound and outbound tunnels , so what is the risk of possible overcommit here?
orignal
same tunnels
orignal
sorry same thread
orignal
you migh want to use multiple threads
orignal
e.g. thread per dest
orignal
beside it it's use frequently
SlippyJoe
so why does libtorrent limit the sam bridge tunnels then ? is it due to a limitation of libtorrent or a i2p spec / sam bridge thing?
SlippyJoe
spawning multiple processes using the same sam bridge but different config otherwise will be fine ?