Reuse proxy backend sessions within requests - #4860
Draft
jakekaplan wants to merge 1 commit into
Draft
Conversation
🤖 Generated with OpenAI GPT-5.6
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.
Proxy component resolution and execution previously opened separate backend client lifetimes, so one frontend call could negotiate with the backend more than once.
ProxyProvidernow lazily retains one isolated backend session for the root request and disconnects it during request cleanup; concurrent requests remain isolated and local component calls do not wake the backend.The default is request scope, while stateful integrations can preserve their deliberate connection lifecycle explicitly:
🤖 Generated with OpenAI GPT-5.6