Great to see this technology is ready nowadays and can be used for production systems :)
On the other hand, ZMQ for the backend is just a pure pleasure and I haven't had a single failure of my components for more than 1 million real requests involving many ZMQ backend interactions.
Though to be fair, we were making it a bit complicated by suspending/resuming the OpenVZ containers. From that we sometimes got dead ZMQ connections that were black holing all traffic (incredibly hard to debug - ended up switching because of it).
- Is mongrel2 getting good development? The latest release was in June, and the latest commit in the canonical repo seems to be from July...
- Is there good support for RFC-version WebSockets yet?
- Is there easy/performant stuff for simple asset serving via mongrel2, or should I use nginx for that?
2. The same, in the develop branch, there are still some questions on how to best implement it like which parts must be done by the handlers and which by Mongrel2, but the coders involved are good and very pragmatic, I bet the results will be a high quality implementation.
3. http://notes.ceondo.com is served by the "Dir" handler, that is, direct static files from disc without going through the asynchronous ZMQ based sequence. It is pretty fast.
Looking forward to your explanation.