HTTP stream internal API #5747
Merged
HTTP stream internal API #5747
Conversation
This file contains hidden or 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
vietj
force-pushed
the
http2-simplification
branch
from
e4eb226 to
6cacf8f
Compare
vietj
force-pushed
the
http2-simplification
branch
from
6cacf8f to
176ee0a
Compare
…ouple Http2ServerRequest/Http2ServerResponse from Http2Stream* API to use instead HttpStream internal API.
… HttpServer(Request|Response)Impl
vietj
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Introduce an HTTP stream internal API.
Motivation:
There has been an HTTP stream internal API for client (since
HttpClientRequest/HttpClientResponse) has a single implementation and the protocol is implemented by the client stream internal API.There is no server stream internal API since server since we have kept an HTTP/1.1 and HTTP/2 implementations. Yet it would be convenient to have this API in order to eventually provide a stream oriented API.
This will also ease the HTTP/3 implementation to come.