NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Some justification (Score:2)
However now AxKit2 is built I find it much easier to hack on than mod_perl, and not just because I know the internals. Adding a new conf
Re:Some justification (Score:1)
Adding config stuff was pretty bad in mod_perl 1. It's supposedly easy in mod_perl 2, but I've never wanted to add a config directive so it's not something I pay attention to. I really don't use any of the Perl config stuff in mod_perl at all. It just doesn't appeal to me.
Profiling, quick restarts -- well, they work for me in mod_perl. (This reminds me of working at a place that used IBM WebSphere, where restarting the dev tools to pick up a code change took 10 minutes! What a pig that thing was.)
You might be able to get the best of both worlds on the auth front by using AxKit2 as your application server and proxying from an apache2 front-end that runs an auth plugin. I do this with mod_auth_tkt, which lets me keep the actual auth code in Perl but have the proxy do the auth checks on static files. You'll lose the simplicity of your setup though.
Reply to This
Parent
Re: (Score:2)
Another option I'm