Xuanwo commented on issue #4286: URL: https://github.com/apache/opendal/issues/4286#issuecomment-1968355973
Thanks for raising the issue! I'm open to switching our HTTP client from reqwest to hyper, which offers us greater control over the underlying HTTP operations. I can see the following benefits: - Upgrade to hyper 1 for now (good to our users dependences) - More control on http (like in mentioned by OP) - Async Runtime Agnostic Based on our current codebase, here are several notes: ## Good OpenDAL wraps all http client side code in [http_util](https://github.com/apache/opendal/tree/main/core/src/raw/http_util), we don't need to replace every usage of http client. ## Bad OpenDAL now relies on features provided by reqwest: - system proxy (should be simple I guess) - HTTP Upgrade (from http/1.1 to http/2) - HTTP 1.1 Keep Alive (a.k.a connection pool) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
