hunger
Non-async client backend feature?
First of all, this crate is great, and the code is very clean, so thank you.
It would be nice to have the option to use simple blocking io instead of pulling in tokio and reqwest which are rather heavy dependencies. For a client that is only expected to have a small number of active connections (probably less than 50), there isn't really going to be much difference between blocking io + threads and asynchronous io.
Would you be open to this?
I will probably not have the time to do it, but I would gladly accept a contribution.
Since I switched jobs, I have hardly gotten round to work on the crate I want to use this one for... so there is even less time to look into this little crate.
