Stefan de Konink dijo [Wed, Oct 22, 2008 at 12:20:16AM +0200]: > > I partly agree with you on a point. But from my own experience with > Cherokee where I really create applications inside Cherokee instead > of 'external' one it is *extremely* simple to create an > extension. If you then look at what is possible and the performance > gain you can get by using Cherokee as an application server itself > it might be feasible for some people to code C for the web again ;) > > In that perspective you could try to create handler_java, that is > able to server request, and use another instance of cherokee to do > the actual load balancing on a different system, which make it > scalable.
Heh... I was bitten by mod_perl not being portable - I just cannot replace Apache, as I have several mod_perl-based applications I developed over the years. Modularity is nice, modularity is your friend. Stick with modularity. Say no to vendor-specific modules :-) 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
