Closed LuKks closed 1 year ago
@kasperisager right now it tracks new connection, disconnect AND when the .connecting prop changes. it will also emit later when the nat info changes (pending the dht-rpc pr)
@mafintosh Makes sense!
Current limitation: when we receive a server connection then socket is already 'open'
, so we couldn't track .connecting
for server connections (needs HyperDHT changes?), it's still ok because I think we're more interested on client connections
Btw I will move the retry timer
test to the other PR where is a bit more relevant
@kasperisager rebased now, in case you would like to confirm
@LuKks @mafintosh From the looks of it, isn't the only additional information provided by this event a way to determine when clients disconnect?