This question builds on #320 and #395 (comment)
I do not see hyper as being a direct competitor to either nginx or h2o, but rather as an http parser powering a potential competitor. In that light, it is more similar to something like https://github.com/h2o/picohttpparser, which powers h2o.
What I'd like to ask is how far away is hyper from this goal, and is there anything left to learn from nginx's http parser and picohttpparser, other than using aio and SIMD? Maybe reusing allocations or pooling them in an arena for the request lifetime and destroying them in one go?
Just for completeness, there is a somewhat newer presentation on h2o than what was posted in #320 that might be interesting:
http://www.slideshare.net/kazuho/h2o-making-http-better
This question builds on #320 and #395 (comment)
I do not see hyper as being a direct competitor to either nginx or h2o, but rather as an http parser powering a potential competitor. In that light, it is more similar to something like https://github.com/h2o/picohttpparser, which powers h2o.
What I'd like to ask is how far away is hyper from this goal, and is there anything left to learn from nginx's http parser and picohttpparser, other than using aio and SIMD? Maybe reusing allocations or pooling them in an arena for the request lifetime and destroying them in one go?
Just for completeness, there is a somewhat newer presentation on h2o than what was posted in #320 that might be interesting:
http://www.slideshare.net/kazuho/h2o-making-http-better