Investigate inbound HTTP message deframing - #6353
Draft
vietj wants to merge 3 commits into
Draft
Conversation
vietj
changed the title
vietj
force-pushed
the
inbound-queue-budget
branch
from
September 10, 2026 13:13
ec1e350 to
f7d69f9
Compare
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
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.
Motivation:
Let HTTP streams provide a pluggable message deframer of pooled buffers instead of implementing it on top of the HTTP API.
The following can be retrofit:
Server side HTTP/1.x has no implementation and relies on a custom implementation of
HttpServerRequestinstead of providing anHttpServerStreamimplementation, thus it would need to be rewritten or written.Status:
Investigation, for further use, targetting 5.3