I guess the problem is that Apache does everything, and the price for that is that it isn't very streamlined.
I may be totally off base because I really don't know that much about non-Apache web servers. Please explain how these new generalized web servers like Mongrel2 would provide a significant advantage over existing web servers like Apache.
I should be able to just execute "server.run(application, port)" or whatever, not have to dive into Apache configuration files. Even with Mongrel2 you need to start multiple processes to get anything working.
As a side note, the current design is definitely POC level, so keep tracking it and if it goes off in a stupid direction let me know.
I'd like a simple, efficient, scalable HTTP server written in C ...
Check out libebb - http://tinyclouds.org/libebb/. It was created by Ryah Dahl (node.js fame) and is a solid piece of software. We used it in our WebROaR server for ruby web applications.Sidenote: libebb's Ragel based parser is derived from Mongrel.
Your language still must efficiently implement some protocol to talk to Mongrel2, whether that's HTTP, 0mq, or some custom binary protocol, right?
I'd like a simple, efficient, scalable HTTP server written in C (or C++ I suppose) that I can write multiple language bindings for. Is this feasible? Is there anything like that out there?