Simplifying the dependency tree

[emilk]

Hello, and thanks for an awesome crate!

I'm interested in replacing the use of reqwest with ehttp.

The advantage is a lot less dependencies. reqwest brings in a huge tree of dependencies, including tokio, while ehttp depends only on the minimal ureq. This in turn translates to faster compile times and smaller binaries.

Would you be open to a PR making such a change?

[podusowski]

Hi Emil, thanks!

Sounds interesting, but last time when I was choosing between two, ehttp didn't support multiple downloads, not sure if that changed? Also, walkers do HTTP cache though http-cache. But if these are addressed, I see no reason not to accept it.

[emilk]

Awesome! Yeah, it will require some work for sure.

What do you mean by "support multiple downloads" though? Downloading multiple files in a single HTTP GET?

[abey79]

A possible avenue might be to split the tile download/cache part from the rendering part, and make the former optionally swappable by a custom implementation.