This repository has been archived by the owner on Aug 23, 2019. It is now read-only.
fix: create separate events for connection tracking #328
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.
The
peer-mux-*
events are currently used for both connection tracking and muxed connection tracking. This creates a problem for the Connection Manager because it won't be able to track unmuxed connections.The Connection Manager should be aware of all connections that are created and closed. This adds events for libp2p and subsequently the Connection Manager to hook into.