relay first, holepunch later #177
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
billiegoose
requested review from
mafintosh and
andrewosh
and removed request for
mafintosh
|
TODO: add test Submitted for review to generate discussion. |
|
punting this as part of the major "don't treat the LAN differently" future change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently the swarm doesn't greedily use relays and then switch over to the holepunched connection. I don't know if that's the behavior we want but if it is, then this is my attempt to rectify that.
Given that
hyperdhtcurrently STOPS holepunching if a LAN connection is relayed, this could drastically increase the load on the relays unless that behavior is also fixed.