Wire spec version 3 #253
Draft
Wire spec version 3 #253
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
|
You can ignote the v2 file for now. I just have to rebase when v2 is merged. |
rachmatowicz
force-pushed
the
wire-protocol-v3
branch
from
055bf88 to
68177d6
Compare
rachmatowicz
force-pushed
the
wire-protocol-v3
branch
from
68177d6 to
c8f7f52
Compare
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.
This is a draft of the wire spec version 3 protocol. I'm still thinking about a few issues, so it is in draft status.
It's important to make a distinction between the wire protocol spec version 3 itself and how the spec will be implemented, interoperating with v1 and v2. They will need to address separate issues at times.