4 ms·
I've been working on implementing a solid HTTP library in Rust, currently at http://github.com/chris-morgan/rust-http http://github.com/chris-morgan/rust-http.
by chrismorgan 13y ago
I've been working on implementing a solid HTTP library in Rust, currently at http://github.com/chris-morgan/rust-http http://github.com/chris-morgan/rust-http. Servo has been using Joyent's HTTP parser and this is a problem that I had observed with it. Yes, it is pretty badly implemented, but it's not a mess because of the style of code—that's for performance. It's only a mess because it's inconsistent and incorrect.
Reading the HTTP method in a high-performance way does lead to superficially ugly code. That's why code generation is good. Ragel has been mentioned and I intend to seriously consider using it, but for the moment my own HTTP method reading code is generated with:
generate_branchified_method(
writer,
branchify!(case sensitive,
"CONNECT" => Connect,
"DELETE" => Delete,
"GET" => Get,
"HEAD" => Head,
"OPTIONS" => Options,
"PATCH" => Patch,
"POST" => Post,
"PUT" => Put,
"TRACE" => Trace
),
1,
"self.stream.read_byte()",
"SP",
"MAX_METHOD_LEN",
"is_token_item(b)",
"ExtensionMethod(%s)");
This is pleasantly easy to read and meaningful.
This generates the high performance artwork shown at http://sprunge.us/HdTH http://sprunge.us/HdTH, which supports extension methods correctly. (Rust's algebraic data types are marvellous for many things in implementing such a spec.)
- masklinn 13y ago> Ragel has been mentioned and I intend to seriously consider using it Have you seen that there's a project for a Rust backend for Ragel[0] which would allow direct reuse of the Mongrel HTTP 1.1 ragel spec? [0] https://github.com/erickt/ragel https://github.com/erickt/ragel
- steveklabnik 13y agoAs a Rust, Ruby, and HTTP enthusiast, this gets a hearty +1 from me as well. It's been a while since I checked out the Ragel backend, does it still generate decent Rust code?
- masklinn 13y agoI have no idea, I've never used it.
- chrismorgan 13y agoYes, indeed. Discussing what I was doing with rust-http in #rust is what got erickt to update that to the current state of Rust development. I would not be using the Mongrel spec directly for licensing reasons. I want the entire thing to be MIT + AL2. I don't know if it ends up the most efficient. I'll see when I get to experimenting around that.