Jeremiah Senkpiel
Jeremiah Senkpiel
@joshtriplett Could you rebase?
@joshtriplett If we release this, is cargo smart enough to not upgrade someone to this version if they are pinning to a previous http-types for some reason?
Confirmed working: https://github.com/http-rs/surf/issues/321#issuecomment-908750099
@sagebind if you wouldn't mind, I'd like to know if this patch looks correct to you.
Bumping a major here likely means bumping a major in surf, which I'd like to avoid until I have to for http-types 3.0 if possible.
You'll need to figure out how to implement it for the async-h1 client. You might need an atomic counter of some sort on the client.
I suspect it should probably be it's own crate.
I don’t think anything would change other than the removal of the intermediate crate.
You can still run surf with the hyper backend...?