[Catalyst] Fast CGI vs ModPerl

[Renaud Drousies]

In my opinion, I'd say that the main disadvantage of running a mod_perl
application is that your application runs with the webserver's
credentials, which means that:

- Any security hole means your whole webserver can be compromised
- If you need your catalyst app to access some ressources, then the
user/group the webserver is running as must be granted access to those
ressources.

However, that could be fixed again with a dedicated instance of a mod_perl
enabled apache.

Renaud Drousies

>> Which of Fast CGI and mod_perl do you recommend for using with Catalyst?
>
> FastCGI.  The problem with mod_perl is that your application gets loaded
> into *every single Apache process*, which is a waste of memory.   I
> think mpm_event and mpm_worker mitigate this waste, but your app needs
> to be thread-safe.
>
> If you want to use mod_perl, the best thing to do is to setup two apache
> instances -- one that serves static pages and proxies requests to the
> backend, and one backend apache that runs mod_perl.  It's a solid setup,
> but not the easiest thing to do.
>
> I find fastcgi pretty easy to set up:
>
> http://www.catalystframework.org/calendar/2006/4
>
> --
> package JAPH;use Catalyst qw/-Debug/;($;=JAPH)->config(name => do {
> $,.=reverse qw[Jonathan tsu rehton lre rekca Rockway][$_].[split //,
> ";$;"]->[$_].q; ;for 1..4;$,=~s;^.;;;$,});$;->setup;
>
> _______________________________________________
> List: Catalyst at lists.rawmode.org
> Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
> Searchable archive:
> http://www.mail-archive.com/catalyst@lists.rawmode.org/
> Dev site: http://dev.catalyst.perl.org/
>