On Tue, 8 Jun 2004, James.Q.L wrote:
> Date: Tue, 8 Jun 2004 22:26:15 -0700 (PDT)
> From: James.Q.L <[EMAIL PROTECTED]>
> To: Modperl List <[EMAIL PROTECTED]>
> Subject: Re: mod_perl presence at OSCON (and other CONs) is at danger
>
> Chris :
> > I personally think mod_perl's strengths are in its rich feature set. Only
> > after watching a few of Geoff's talks (and one of Stas's) did I realize
> > exactly what PHP developers are missing. They speak about things like
> > ties, closures, and globs. Plus, PHP is limited to the content generation
> > phase, so mod_perl has a pretty big advantage there. Geoff describes
> > mod_perl as the Apache API in Perl. While this is probably obvious to all
> > of you, it's not something I realized on my own.
>
> we all know there are so many technologies for web programing, ASP,PHP,Python,Java
> etc. what makes
> one choose mod_perl over others? why learn/use mod_perl, why mod_perl instead of php
> etc. a
> section about these on perl.apache.org would be good intro to people who curious
> about mod_perl.
>
> I think php is used more often because it does most of the small to medium projects
> just fine and
> it does easier. at least that's what i heard ( i dont have any expereience on php ).
It appears easy to beginners, but as server admin, I find it a nightmare
for beginners to play with it without knowing what's involved.
So the marketing strategy for mod_perl should be very different. One
can do so much more with mod_perl.
> I also likes Stef's idea about adding user comments for doc. hope it can happen.
>
> hmm, does mod_perl still have problem running for virtual hosts? people choose php
> over cgi for
> obvious reason.
Problem with virtual hosts? Like what?
Regards,
Jie
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
