show if proxing on RemotePeer #994
Open
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
…t.create' 'File' instances
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.
what
exposes
proxyas a flag onRemotePeerinstances passed over PeerWorkerProxywhy
It is very useful to know if another peer is proxying your writes (so you can respectfully slow down for example) ... however the RemotePeer doesn't pass through the proxy value over the worker divide which means this data is unavailable.
note
PR against
nexton RemotePeer proper (not the proxied version), the value of
proxyis a more complex object, which makes this inconsistent when running network withworker:{true/false}... I opted to make it just a boolean for simplicity, but the inconsistency is a bit of a smell, so open to suggestions.