I doubt if anybody is using the mruby handler in production, considering the fact that functions necessary to modify the requests in the handler was committed this week :-)
Libh2o (the protocol implementation) support both libuv and evloop (our tailor-made event loop).
The default event loop of libh2o is libuv, since libuv is popular and has bindings to other protocols (which you would need if you want to implement an application using libh2o).
OTOH the standalone server uses evloop for performance.
5 comments
[ 1.8 ms ] story [ 17.6 ms ] thread* Support for the PROXY protocol
* Support for cache-based and ticket-based TLS session resumption using Memcached (and forward secrecy)
* Experimental mruby Handler
Embedding mruby is an interesting choice. Is anyone known to be using this in production yet?
I doubt if anybody is using the mruby handler in production, considering the fact that functions necessary to modify the requests in the handler was committed this week :-)
The default event loop of libh2o is libuv, since libuv is popular and has bindings to other protocols (which you would need if you want to implement an application using libh2o).
OTOH the standalone server uses evloop for performance.