-
Notifications
You must be signed in to change notification settings - Fork 202
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
Unidirectional and bidirectional streams #885
Merged
Merged
Commits on Oct 12, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 820dd81 - Browse repository at this point
Copy the full SHA 820dd81View commit details
Commits on Oct 13, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 5061a15 - Browse repository at this point
Copy the full SHA 5061a15View commit details -
Configuration menu - View commit details
-
Copy full SHA for a9b13de - Browse repository at this point
Copy the full SHA a9b13deView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4137259 - Browse repository at this point
Copy the full SHA 4137259View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0740371 - Browse repository at this point
Copy the full SHA 0740371View commit details -
Configuration menu - View commit details
-
Copy full SHA for afabe8a - Browse repository at this point
Copy the full SHA afabe8aView commit details
Commits on Oct 18, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 8fe4367 - Browse repository at this point
Copy the full SHA 8fe4367View commit details -
Unidirection and bidirectional streams
This is #872 with some additional exposition and one significant change. Client-initiated streams are now EVEN. Server initiated streams are now ODD. This is a pretty noticeable change, because it inverts the current sign, and might cause some disruption in implementations. However, it makes stream 0 work within the framework better. It wasn't clear what Ryan's intent was with respect to numbering, but I wouldn't have noticed this until I noticed a conflict between prose and the table. Closes #643, #656, #720, #872, #175. This does not close the other issues that were addressed by #643, because this doesn't include any changes in the HTTP draft. I'll create a follow-up PR for that.
Configuration menu - View commit details
-
Copy full SHA for 82f6b87 - Browse repository at this point
Copy the full SHA 82f6b87View commit details -
Configuration menu - View commit details
-
Copy full SHA for f5b735a - Browse repository at this point
Copy the full SHA f5b735aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 442dc99 - Browse repository at this point
Copy the full SHA 442dc99View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3541a42 - Browse repository at this point
Copy the full SHA 3541a42View commit details
Commits on Oct 30, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 665dc8b - Browse repository at this point
Copy the full SHA 665dc8bView commit details
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.