On Tue, 5 Dec 2000, J. J. Horner wrote:
> Perhaps if someone makes a mod_perl based embedded
> scheme like Cold Fusion or PHP, that has some special
> hooks into Apache for performance that the other
> solutions don't offer. . .
how is mason not like this?
> Honestly, though, I didn't believe the strength of
> mod_perl rested on the Mason type modules. I thought
> the strength of mod_perl was having a perl/Apache API.
> Having an easy way to interact with Apache using
> everyone's favorite language was what sold me on Apache.
we very rarely use the apache api anymore. i prefer the
abstraction layer of a templating engine, for ease of use
and for maintainability by larger teams. i used to be
shocked that nobody i worked with wanted to learn how to
configure apache or use its api. now i'm right there with
them. give me Apache::Request and mason and i'm happy.
i know there are several people on the list who swear by
"all handlers, all the time". i've never heard anybody give
a reason for that preference that actually made sense to me.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
