[5.0.3] P2P: Resolve on reconnect #2410
Closed
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.
Resolve address on reconnect. (Take 2, See #2408)
Instead of:
Now you get:
This takes a different approach than #2408. This approach is closer to Leap 4.0 approach to connection lifetime although it does keep the
connections_manager
added in Leap 5.0.Backport of AntelopeIO/spring#853