-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve the documentation for the p2p feature #4894
Conversation
License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM,
One thing to note is that when you p2p stream dial
, the listening endpoint is one-shoot (unlike ssh's -L
). We might want to change this at some point (either by --keep
flag or by just changing default behavior)
Are you sure? It looks like listen dials the listener for every inbound stream (although it looks like there are many obvious bugs...). |
I meant the listening endpoint on the dialer side (the one on client side) - https://github.com/ipfs/go-ipfs/blob/master/p2p/p2p.go#L87. The code is messy/weird there, I'll revisit it eventually to fix some of this stuff (likely when I'll get to creating coreapi for it). |
Ah... I see. Really, we should support an HTTP upgrade from a command (although supporting both makes sense). |
We should make it work like |
@Stebalien is this unblocked yet? cc @magik6k |
I've cherry-picked this in #4929 and adjusted to changes there, so if the refactor pr is going to be merged soon I'd say this can be closed. |
No description provided.