Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So
peer:connect
andpeer:disconnect
are a bit misleading, as they actually have to do with muxed connections and our actual connection status to a peer. This creates problems for things like the Connection Manager that need to know about all connections in order to do its job properly. These events are used by many different things so changing their behaviors and replacing them with more appropriately named events isn't reasonable to do at this point.This introduces two new events,
connection:start
andconnection:end
that can be used by the Connection Manager to better keep track of connections.