Generic HTTP client instead of reqwest

[WhyNotHugo]

Currently this library pulls reqwest as an HTTP client. This is typically a solid choice for applications, but not very flexible for a library, since consumers cannot use an HTTP client which fits their needs.

Would you consider making the HTTP client generic, with bounds something like these¹:

C: Service<http::Request<String>, Response = Response<Incoming>> + Sync + Send + 'static,

This allows using hyper clients. Users who need reqwest can still use it, but users who need to control further details of the HTTP client can also do so. This also substantially reduces the dependency tree, since reqwest is a pretty "fat" dependency.

Footnotes

1. This specific sample is actually copied from libdav's CalDavClient. ↩

[WhyNotHugo]

Please note that I'm asking whether you'd consider this an acceptable improvement, not whether you're willing to put the work. I believe I might be able to work on this refactor myself.

[WhyNotHugo]

See also: https://sans-io.readthedocs.io/

[mdecimus]

Hi, jmap-client is currently not being maintained but we have plans to rewrite it next year.

[WhyNotHugo]

Can you keep me in the loop when these plans start materialising? I'm interesting in contributing in this.

I'm currently using JMAP for pimsync, also with NLNet.

[mdecimus]

Sure, but work won't start until several months from now as the priority is getting Stalwart to version 1.0.