HTTP Clients

[gsquire]

We could explore using a different HTTP client such as ureq to simplify things. If you think there are better options to the question below, please share your thoughts!

[YeahNotSewerSide]

I find supporting both blocking and async implementations to be a bit weird, the problem is that reqwest library is designed to be asynchronous. An implementation for blocking reqwest is just a wrapper around async implementation. As a user, I was only using async implementation, and when for some reason asynchronous is needed I think it's up to user to create a local executor and run the requests using it

[YeahNotSewerSide]

Also an asynchronous client has a better performance, again due to blocking one being a wrapper

[junbl]

I only use the async implementation. Using ureq (and therefore I assume only including a blocking implementation) would be definitely be a drop in usability for me
I think the current library does a good job of abstracting away the underlying http library, at least for simple use cases. I'm used to reqwest but I haven't had a reason to interact with the underlying client directly when using Sender.

[gsquire]

I thought offering ureq in place of the current blocking client would trim down dependency size for those who don't use tokio already. I won't remove the default (asynchronous) client.