3 ms·
As the author of H2O, I would like to leave a comment here. First of all, the development is still in early stages, please forgive me for the lack of documenta
by kazuho 12y ago
As the author of H2O, I would like to leave a comment here.
First of all, the development is still in early stages, please forgive me for the lack of documentation.
That said, below are some high-level design issues that are not addressed by the README.
- it is designed to be pluggable (though not as flexible as Apache), by providing virtual-host-based configuration of generators, output filters and loggers
- lib/file.c and lib/chunked.c would be a good place to understand their interface if you are interested
- I am (at the moment) not interested in providing support for input filters
- performance of HTTP parser is likely going to become importance since the ratio of small files being served is expected to increase in HTTP/2; H2O is designed with that in mind
- tinco 12y agoWhy is H2O faster than nginx? I've read the source of nginx and it does attempt to be very clean and tightly optimized, which makes me suspicious of H2O. Is there some big architectural advantage or is it less robust in some way?
- kazuho 12y agoPlease read my other comment here https://news.ycombinator.com/item?id=8342684 https://news.ycombinator.com/item?id=8342684