Re:Announcing the `http` crate
by JoshTriplett on Monday July 31, 2017 @10:51PM
(#14897571)
I wouldn't be surprised if an "http-parser" crate pops up on top of this. But unlike the http crate, an http-parser crate would have to make at least one potentially controversial choice, namely "which parsing library".
Re:Announcing the `http` crate
by steveklabnik on Tuesday August 01, 2017 @09:44AM
(#14900482)
I've been working with this crate for a while, and use https://crates.io/crates/httparse with it, it works pretty well.
>It does not cover transport, but is rather intended for use in libraries like Hyper, and to support an ecosystem of crates that can share HTTP-related types.
So I don't think they added any implementation details to the crate itself, to avoid people taking issue with something being too bloat-ey or not to their need, and rejecting the common types, which seem to be the real goal. It does seem like something you'd always need, though - I can only imagine that a proper parser would be pretty large, and they didn't want people to complain about it.