Hi there! I am going to try to explain why I made the decision for dropping the u-Cherokee support. There are a couple of reason that I would like to share with you:
- First of all, it did not seem to be one of the most successful efforts of the project. Most of the people have been focused on the performance and the fastcgi/scgi support rather than on the embedded version. Basically, I dropped u-Cherokee from trunk because I was trying to focus the efforts on the most popular pieces of Cherokee and get rid of the parts that were not attacking users and developers to the project. - From the technical point of view, Cherokee is quite lightweight. Did you guys remember that Nokia phone (not the 770) that runs Apache? Let's face it, if a cell phone is able to run such a huge monster, almost any embedded device ought to be able to run Cherokee, don't you think? :-) Besides, there is a little - let's call it - "trick" that you can use to build a custom Cherokee web server. If you execute the ./configure script with the --enable-static-module parameter, you will able to compile a set of custom plug-ins into the main server library. In that way, you can get rid of the rest of the plug-ins that you don't use, and therefore get a customized binary that I reckon would be roughly the size as u-Cherokee. For instance, if you only use CGIs and static files without loggers, validators, balancers or encoders in your embedded device, it would be something like this: ./configure --enable-static-module=file,cgi And after compiling the server you could just remove libplugin*, and you should be fine, actually. Anyway, I am open the discuss all this stuff and check how we could work with OktetLABS to make Cherokee a better embedded server. Cheers! -- Greetings, alo. _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
