thrift proxy: move UpstreamRequest into its own file#17498
Merged
zuercher merged 3 commits intoenvoyproxy:mainfrom Jul 27, 2021
Merged
thrift proxy: move UpstreamRequest into its own file#17498zuercher merged 3 commits intoenvoyproxy:mainfrom
zuercher merged 3 commits intoenvoyproxy:mainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 is needed so that it can be reused by the upcoming shadowing
implementation, which will introduce a dependency from Router to
ShadowRouter to UpstreamRequest, so this breaks the circular
dependency.
I have one more PR (4/5) that moves common functionality from
Router to RequestOwner. After that I'll send over
the actual shadow routing implementation, which reuses all of
these parts.
Signed-off-by: Raul Gutierrez Segales rgs@pinterest.com