>
> 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.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
