You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In scope of the #1225, the repository-azure is switching to Azure v12 SDK, using Netty as underlying HTTP transport client. However, Azure v12 SDK also supports OkHttp client and it might be beneficial to provide the way to using this one instead.
Describe the solution you'd like
Allow to configure the underlying HTTP transport client: netty or okhttp. It should be able to be implemented as a new transport module (transport-okhttp) alternative to transport-netty4.
Describe alternatives you've considered
N/A
Additional context Okio is leaking threads (square/okio#107) as well as OkHttp (square/okhttp#6173) so it will incur some workarounds in order to properly test Azure v12 SDK with OkHttp client.
Is your feature request related to a problem? Please describe.
In scope of the #1225, the
repository-azure
is switching to Azure v12 SDK, usingNetty
as underlying HTTP transport client. However, Azure v12 SDK also supportsOkHttp
client and it might be beneficial to provide the way to using this one instead.Describe the solution you'd like
Allow to configure the underlying HTTP transport client: netty or okhttp. It should be able to be implemented as a new transport module (
transport-okhttp
) alternative totransport-netty4
.Describe alternatives you've considered
N/A
Additional context
Okio
is leaking threads (square/okio#107) as well asOkHttp
(square/okhttp#6173) so it will incur some workarounds in order to properly test Azure v12 SDK withOkHttp
client.CC @nknize
The text was updated successfully, but these errors were encountered: