Repository navigation
feat(proxy): support transport-owned upload pacing - #11
Closed
rkaplan-hub wants to merge 3 commits into
Closed
rkaplan-hub wants to merge 3 commits into
rkaplan-hub wants to merge 3 commits into
Conversation
Signed-off-by: kaplan <rkaplan@redhat.com>
Signed-off-by: kaplan <rkaplan@redhat.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
Signed-off-by: kaplan <rkaplan@redhat.com>
This was referenced Nov 10, 2026
rkaplan-hub
marked this pull request as ready for review
November 10, 2026 18:07
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
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.
Large filtered upload chunks currently have one release point, so an application cannot pace bounded portions at the upstream writer or retain ownership until those bytes are accepted.
Add an optional
ProxyHttp::request_body_pacerhook returning an ownedRequestBodyPacer. HTTP/1 retains it in the request pipe and admits prefixes while continuing to poll upstream responses. HTTP/2 admits prefixes at its DATA writer. Both paths preserve the final end marker and settle accepted payload on errors or cancellation.Add an opt-in HTTP/1 controlled writer and HTTP/2 accepted-DATA counters so partial progress survives interrupted writes, excluding HTTP framing. The default pacing hook returns
None.This supports praxis-proxy/praxis#124 and the runtime/integration work in praxis-proxy/praxis#1510 and rkaplan-hub/praxis#1. Praxis pins the exact fork revision until this API is released.
Validation: