Hi, there:
just subscribed to this advocacy list.
First, sorry to Frank. I was replying his email in the user list
but was wrongly put his address as the subject. :-(
Please let me share some of my experiences in using mod_perl.
There are four factors when choose a particular language:
1) easy to program
cgi is very easy to use, and php is easy. mod_perl and
java servlet are hard.
2) speed
mod_perl is fast but php is fast too (if not faster),
and so is Java servlet.
3) capacity/scalable
mod_perl is very scalable --- I mean, one can properly
config a single server to handle dynamic content for
200K daily unique IPs. PHP may end up with just 100K
and servlet ends up at around 50K.
However, even the old CGI can handle 20K unique IPs
with a new CPU. Since most sites won't
need to go above 20K IPs, this advantage is not that
attractive in practice.
And what is worse is that the current existing mod_perl
toolkits seem not scalable when compared to PHP. I knew
2 cases where people gave up the mod_perl toolkit
and turned to PHP.
4) easy to manage, work as team
both mod_perl and servlet are good to be written in OO
(and the so-called MVC). PHP is bad.
But again, majority webmasters don't need OO or MVC.
5) learning curve, friendly environment, existing applications etc.
PHP is the best, then serverlet; mod_perl is the worst.
Based on the above situation, we see that the potential mod_perl
users are those who are using or will choose Java servlet,
and advanced PHP users who need the projects to be in OO and MVC.
To advocate mod_perl, the priorities rank as:
1) focus on mod_perl's ability of OO / MVC
2) scalability (only the original mod_perl, not toolkits)
3) and speed
4) avoid toolkits but diretly go to XHTML.
POD MERL
---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe@perl.apache.org
For additional commands, e-mail: advocacy-help@perl.apache.org
just subscribed to this advocacy list.
First, sorry to Frank. I was replying his email in the user list
but was wrongly put his address as the subject. :-(
Please let me share some of my experiences in using mod_perl.
There are four factors when choose a particular language:
1) easy to program
cgi is very easy to use, and php is easy. mod_perl and
java servlet are hard.
2) speed
mod_perl is fast but php is fast too (if not faster),
and so is Java servlet.
3) capacity/scalable
mod_perl is very scalable --- I mean, one can properly
config a single server to handle dynamic content for
200K daily unique IPs. PHP may end up with just 100K
and servlet ends up at around 50K.
However, even the old CGI can handle 20K unique IPs
with a new CPU. Since most sites won't
need to go above 20K IPs, this advantage is not that
attractive in practice.
And what is worse is that the current existing mod_perl
toolkits seem not scalable when compared to PHP. I knew
2 cases where people gave up the mod_perl toolkit
and turned to PHP.
4) easy to manage, work as team
both mod_perl and servlet are good to be written in OO
(and the so-called MVC). PHP is bad.
But again, majority webmasters don't need OO or MVC.
5) learning curve, friendly environment, existing applications etc.
PHP is the best, then serverlet; mod_perl is the worst.
Based on the above situation, we see that the potential mod_perl
users are those who are using or will choose Java servlet,
and advanced PHP users who need the projects to be in OO and MVC.
To advocate mod_perl, the priorities rank as:
1) focus on mod_perl's ability of OO / MVC
2) scalability (only the original mod_perl, not toolkits)
3) and speed
4) avoid toolkits but diretly go to XHTML.
POD MERL
---------------------------------------------------------------------
To unsubscribe, e-mail: advocacy-unsubscribe@perl.apache.org
For additional commands, e-mail: advocacy-help@perl.apache.org