-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClientModel Prototype: Move response buffering to transport #41651
ClientModel Prototype: Move response buffering to transport #41651
Conversation
API change check APIView has identified API level changes in this PR and created following API reviews. |
…core2-move-buffering-to-transport
…core2-move-buffering-to-transport
_transport = new AzureCorePipelineTransport(this); | ||
} | ||
|
||
internal void ProcessInternal(HttpMessage message) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This effectively retroactively implements the template method and allows us to use ClientModel PipelineTransport validations in the Azure.Core abstract transport type. This gives us buffering in the default pipeline even for custom subtypes of HttpPipelineTransport.
…core2-move-buffering-to-transport
Closing in favor of #41907 |
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.