@Xeha
@orignal
Arch
BubbRubb
C341
Daddy
Danny
Irc2PGuest43584
Irc2PGuest52828
Irc2PGuest82088
Irc2PGuest89751
Meow
Over
R4SAS
RN
RN_
SigSegv
SlippyJoe_
StormyCloud
acetone
aisle
ardu
b3t4f4c3___
duanin2
eyedeekay
hagen
halloy13412
hk
ka2
mareki2p
poriori
qend-irc2p
r00tobo
r00tobo[2]
rapidash
semantica
shiver_
thetia
u5657
weko
wew
woodwose
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 ?