Skip to content
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

protocols/plaintext: Do not UVI encode goodput #1765

Merged
merged 3 commits into from
Sep 17, 2020

Conversation

mxinden
Copy link
Member

@mxinden mxinden commented Sep 16, 2020

Only prefix handshake messages with the message length in bytes as an
unsigned varint. Return a plain socket once handshaking succeeded.

Tested compatibility with https://github.com/mxinden/libp2p-perf.

Fixes #1760

Only prefix handshake messages with the message length in bytes as an
unsigned varint. Return a plain socket once handshaking succeeded.
Copy link
Contributor

@romanb romanb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Hopefully the specs can be clarified. It is curious that this hasn't come up before. I was probably naively assuming compatibility was tested earlier in the context of #1236, or maybe the other implementation(s) actually changed afterwards?

@mxinden
Copy link
Member Author

mxinden commented Sep 17, 2020

Hopefully the specs can be clarified.

I have opened libp2p/specs#295.

or maybe the other implementation(s) actually changed afterwards?

As far as I can tell from the initial pull request libp2p/go-libp2p-core#37 the Go implementation only UVI encoded the handshake messages .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

protocols/plaintext: Incompatible UVI encoding with Go implementation
2 participants