Flush control frames; don't flush user frames. #505
Merged
+5
−1
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
|
LGTM |
codefromthecrypt
pushed a commit
that referenced
this pull request
Feb 2, 2014
…sh-user-frames Flush control frames; don't flush user frames.
codefromthecrypt
deleted the
flush-control-frames-dont-flush-user-frames
branch
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 change fixes a bug where during a bench, MockWebServer got an EOFException trying to read the http/2 connection header.
Let the application layer decide when to flush on data. Ideally we flush when we're done sending a full request (headers and body), and that's all. Control frames, such as the connection header need to by flushed immediately.