This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: RFC: mod_perl advocacy project resurrection From: "Gerald Richter" <richter@ecos.de> Date: Tue, 5 Dec 2000 21:47:03 +0100 i don't have figures, but from experience i know - once i've > compiled httpd, i have almost no real configuration work to > do with php. on the other hand, if i want to set up mason, i > have to write 10-20 lines of perl code and access them with > PerlModule or PerlRequire. if i want multiple mason sites i > have to dig back into that perl script. certainly not > difficult, but kinda irritating, and takes more effort to > maintain, especially across multiple machines. > That's what I always tried to avoid within the configuration of Embperl. I have tried to keep it as simple as possible for the first start. If you have mod_perl up and running, you just tell Apache to handle for example .epl files by HTML::Embperl and your are done. (exactly 6 lines to copy and paste form the Embperl docs into yout httpd.conf ), but as I understand Jonathan he (and Mason) has a slightly other intention in this area. ===