06chaynes
Use http-1.0.0 for http-cache-tower
WIP branch for updating the refactor branch to use http-1.0.0, per our discussion in https://github.com/06chaynes/http-cache/issues/4.
If accepting the Clone bound on ReqBody is acceptable, it simplifies the passing of the request to the future quite a lot.
If this looks promising to you, I can also try to tackle updating the future into a state-machine so that we can poll other futures inside of it. I know the refactor branch is quite far behind the main branch though, so if it makes more sense to work off of that one, let me know. I might need some pointers in terms of which methods need to be called inside the future since I'm not too familiar with http-cache internals.
Pushed a new branch that I think might ease this implementation a bit, at least I think it might in regards to running the async code blocks https://github.com/06chaynes/http-cache/tree/remove-async-trait
One prerequisite to merging this will be the Reqwest update to use hyper v1.0.0, which thankfully seems to be underway here https://github.com/seanmonstar/reqwest/tree/hyper-v1
After updating in my local branch everything but the http-cache-reqwest crate seems to be good to go, so once Reqwest itself is updated it should be fairly straightforward to complete on this end.
Sweet, reqwest has been updated. Just need a new reqwest-middleware release and this particular change should be about ready
@06chaynes It seems that
reqwest-middlewarehas been released
That comment was in regards to updating http, which has already been merged in