@Xeha
@orignal
Arch
BubbRubb
C341
Danny
Irc2PGuest13075
Irc2PGuest16460
Irc2PGuest21077
Irc2PGuest39074
Irc2PGuest44715
Irc2PGuest5779
Irc2PGuest88711
Meow
R4SAS
RN
RN_
SigSegv
Stormycloud
acetone
aisle
ardu
b3t4f4c3__
duanin2
eyedeekay
hagen_
halloy13412
poriori
qend-irc2p
r00tobo
r00tobo[2]
rapidash
semantica
shiver_
thetia
u5657
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 ?