In many regards, Cherokee, besides being one of the faster, it’s probably the most innovative open (and maybe closed as well) source web server out there too. (And no, I don’t think this because it’s developed and maintained by my friend and co-worker alo).
I could give you tons of examples of this, but to be honest, the things that I like the most, it’s its approach towards simplicity and easy of use. Its motto could perfectly be:
"A web server for human beings."
Now, most of the coolest features are already on the SVN trunk waiting for the 0.6 release, but there’s one problem, there’s a show stopper feature not implemented. And probably the most important.
0.6 has been designed with one assumption, users won’t edit the configuration file, Cherokee will provide an administrative interface to do so. When alo told me about this idea, I said, wow, that’s actually what any web server should provide for configuration purposes, it makes a lot of sense.
It turns out that I’m a pretty lame web developer, I’m uncomfortable at HTML and JS, I’m quite frustrated, however I’m enjoying the experience of writing the web service side for the asynchronous calls.