Skip to content
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

Conversation

annelo-msft
Copy link
Member

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.

@azure-sdk
Copy link
Collaborator

azure-sdk commented Jan 29, 2024

API change check

APIView has identified API level changes in this PR and created following API reviews.

Azure.Core
System.ClientModel

_transport = new AzureCorePipelineTransport(this);
}

internal void ProcessInternal(HttpMessage message)
Copy link
Member Author

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.

@annelo-msft
Copy link
Member Author

Closing in favor of #41907

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants