> . Since > lots of people have set their server automatically upgrade in order to > prevent security hole, they might run into that their servers are down > without any notifications. If you would like to let cherokee to be > mature enough to be commercial product, you should fix the big bug > immediately in the upstream asap.
+1. We had to switch to nginx for similar reasons. The rewrite rules made it borderline, since idiotically, php developers assume apache and mysql, and do not write server agnostic code, but I could have argued ( and did I! ) passionately about the sins of the fathers not being visited upon we the children. Still , a new webserver should be able to do most of the redirections that existing webservers do. But the lack of a development vs stable branch or similar like say, zsh: i zsh - A shell with lots of features p zsh-beta - A shell with lots of features (dev tree) p zsh-beta-doc - zsh beta documentation - info/HTML format I'd love to see: i cherokee p cherokee-dev is kind of essential for an up and coming webserver. _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
