Perrin Harkins wrote:
> I don't think this changes your situation any. CGI is not really
> fast enough to use, so you still need mod_perl or FastCGI. Because
> the current crop of linux distros came out before mod_perl 2 but
> couldn't use mod_perl 1 (since they are using apache 2), they have
> poor mod_perl support in their packaging systems. You can wait for
> the next round, or build your own packages, or use an OS like FreeBSD
> which has a more up-to-date package. You can also try FastCGI or
> SpeedyCGI, but I don't know what the situation is like with packages
> for them.
I've asked for "system requirements" on the Catalyst mailing list:
http://lists.rawmode.org/mailman/listinfo/catalyst
and tentatively plan to use the Debian 3.1 stable apache-perl package (Apache
1.33 and mod_perl 1.29).
> In my experience, supporting other people's apache builds is hard,
> and it's much simpler to give them a package that installs somewhere
> other than /usr/local/apache and runs on a port other than 80. Then
> they can proxy to it from their crazy apache build and you don't have
> to make your stuff work with someone else's out-of-date and broken
> stuff.
Thanks for the warning and advice. :-)
David
