-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Lionel MARTIN wrote:
> I decided to go for Mason 1.31, which is using CGI as "args_method", by
> default for HTML::Mason::ApacheHandler, instead of "mod_perl" for
> version prior to v1.30.
So after all my previous message was a good guess, but your statement
leaves an open point: did you on the "non functional version" specify
somewhere to use "mod_perl"? If true, given the fact you don't seem to
know anything about libapreq2, there should have been a fatal error.
So I presume there were more inexactitudes in your previous
"specifications" :(
> I can't really understand why, and what is the difference between these
> options ("mod_perl" VS "CGI", but at least, this did the job right..
> I think there's a bug somewhere, when using "mod_perl".
There is not bug.
> So, I'll be using CGI for now.
> Is there a performance penalty doing that?
Huge. Understanding what's mod_perl, libapreq and how do they integrate
with Apache's httpd server will clarify why.
- --
Marius Feraru
-----BEGIN PGP SIGNATURE-----
iD8DBQFEFqlftZHp/AYZiNkRAqhrAKCHdFCGPO2MQQU9qKRNc3MdrBAESACeLbFb
hNsqSk2q+ojaxLxPCj2320c=
=uGFG
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
