Julian dijo [Tue, Oct 21, 2008 at 04:07:27PM -0600]: > are ther some documentation for constructing cherokee modules ?, for trying > to rewrite mod_jk for Cherokee ?
Actually, it is not only that Apache's API is naturally not available under Cherokee - But I feel it's a deeper design desition that this kind of modules don't exist in Cherokee. Apache has a very large API, and quite a bit of places where you can hook and build modules from. It is, of course, a very strong and complete offering. But that's part of what has brought to its complexity and unmaintainability - even after the 1.x->2.x rewrite, the project's design and typical usage _requires_ all that. Most modern webservers (Cherokee included) favor you having an application server, and providing just a thin layer - a simple connection (i.e. via FastCGI) from the Webserver to it. This has several advantages, besides sheer code footprint and simplicity - One of them is effective privilege separation. By running separate application servers, connected to Cherokee by a socket or similar means, each of them can run as a different user (even on a different machine), but be managed and accessed from the same single source. Now, I'm _not_ a Cherokee programmer, just a humble packager :-) Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
