On 24 Feb 2008, at 16:18, Jack L wrote: > - proxying to a backend web server (something similar to mod_proxy > in apache and lighttpd)
We have included a generic balancer (named "mirror"). A HTTP reverse proxy *prototype* is kind of working as well, but we are not going to ship it with 0.6; I don't think it's ready for production. Anyway, 'mirror' is perfect is you want to distribute your HTTP load between different web servers that is usually the most common case. > - more flexible fastcgi support (configure by path as well as file > type) > I don't see them in your list. Maybe they have already been > implemented? You can configure FastCGI (as the rest of the handlers) with rules based on the extensions, directories and regular expressions. Moreover, that task has become much easier with the new administration interface that we have developed for this upcoming release. > My other question is, Cherokee has a Windows version. What features > is it still missing in the Windows version compared with the Unix > version? I'm asking since I intend to use it on Windows production > servers. I have been working on different Unix based platforms: OpenSolaris, OS X and Linux. I haven't personally worked on Windows, but there are other developers who have. There are a few missing features on the Windows version though: it does not launch interpreter when it uses FastCGI or SCGI, for instance. I would expect these missing features to be implemented within the first few versions of the Cherokee 0.6.x live time, so my advise to you would be to bare with us until we release a Windows bug-fixing focused release (and we provide tested Windows binaries). -- Greetings, alo. http://www.alobbs.com/ _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
