I'd noticed the article you're talking about a while back when I was first planning this system, but the mod_perl's unfortunately out of the question here. The webserver is pretty heavily loaded as things are =)

Thanks again to all who replied!

Peevish Update To those -- ing: this is a situation not of my making, nor is it in my power to change. I fully realize the benefits of mod_perl, but the scripts I'm writing are among the few Perl scripts actually running on this server. Mostly it's other kinds of content. The web server i's proper functioning is critical, so I understand the reluctance to add any module as complex as mod_perl to it.

Philosophy can be made out of anything -- or less

*boggle*

Let me get this straight. You are not going to mod_perl, whose very reason for being is to do the same thing as CGI scripts do while generating less load because you are too loaded?

That very much looks to me like a decision made by someone who does not understand the technology!

You are the first person to mention CGI, nor is mod_perl all about CGI.

grrr. =)

He wants help with backside log parsing. Doing it in server engine is evil.

--
$you = new YOU;
honk() if $you->love(perl)