Really? Even if you go back to the old NCSA httpd, your looking at at something less than 200 lines.
Do you think it should be an entire Apache-type get-up, or just briefly as one of the examples in Section #1?
I was thinking of going Qt binding in Rust, and a book about that, but ... it doesn't really do anything other than say "Here's how you do C++ interfaces in Rust".
I'll think about the broader issue which you point to -- a good-ish service on a good-ish service bus. Maybe like you would see with Scala on a ZeroQ thing, do you think?
Naturally it wouldn't follow the entire reference and specification but just getting it off the ground handling gets/posts in a psuedo standard conforming way would be a lot.
Also this would cover a lot of the basics of OS interaction, multi-threading, etc.
That's my 2cents. I would love to see more rust books come out. I'll happily buy them. I use the language on and off (primarily jumping between C, Java and Rust (former 2 for work)). Rust's high level programming is very nice and while Java does support some of the things rust does, its not as clean as Rust's syntax.