Is it possible to use IHttpClientFactory instead of RestSharp as an HTTP component?

[yilezhu]

Not long ago, I tested and found that there was a problem of TCP leakage。Later, it was found that the problem was with the RestSharp component.See this issue for details #411 .
restsharp/RestSharp#1406
I tried to migrate the IHttpClientFactory component and found it failed. so is there any official plan to use IHttpClientFactory instead of RestSharp as an HTTP component? Otherwise, this problem will be perplexed all the time。

[harshavardhana]

Not long ago, I tested and found that there was a problem of TCP leakage。Later, it was found that the problem was with the RestSharp component.See this issue for details #411 .
restsharp/RestSharp#1406
I tried to migrate the IHttpClientFactory component and found it failed. so is there any official plan to use IHttpClientFactory instead of RestSharp as an HTTP component? Otherwise, this problem will be perplexed all the time。

We can definitely do this a breaking change as we add new APIs // cc @poornas @kannappanr

[xujiesh0510]

HI. Any progress on this issue？ To be frank, This is not a production-ready library without solving this issue.

[xujiesh0510]

@yilezhu , Have you implemented a simple version of minio-dotnet using HttpClientFactory ?

[BigUstad]

As @harshavardhana remarked. It'd be a breaking change & we'd need to rewrite the APIs. The product development team is looking into it and they will make a decision.

[harshavardhana]

Fixed by #551