Hi, Perrin is right with AxKit you have the following possibilities: - Apache1+mod_perl1+AxKit1 - Apache2+mod_perl2 <=> AxKit2 (maybe a proxy in between)
But there is also Apache2::TomKit (http://search.cpan.org/~tomson/Apache2-TomKit-0.01_6/lib/Apache2/TomKit.pm): - Apache2+mod_perl2+Apache2::TomKit (not that feature rich but e.g. custom providers, cache, transformer-pipeline are working) I plan to make a CPAN-Release by the end of month but the current SVN at http://publicsvn.bestsolution.at/repos/perl/TomKit/trunk/ is stable and can be used. Still as the version number my indicate it's a developer release although we are using TomKit in our production environment since ~ 6 months and don't have any problems. But because it is not thoroughly tested I marked it as a dev-release ;-) Tom Perrin Harkins schrieb: > Boysenberry Payne wrote: >> It seems like they're mutually exclusive technologies. >> >> Can they both be installed in one Apache server to good effect? > > AxKit requires mod_perl. Maybe you mean AxKit2? It has its own HTTP > server and doesn't interact with Apache or mod_perl. There's no reason > you can't run both on the same machine, and proxy parts of your site > from your front-end server to AxKit2 instead of mod_perl. > > - Perrin
