It's going to be a very tough sale (and an almost completely uphill
battle) to sell JServ to an existing mod_perl shop.
If they're good enough to use mod_perl effectively, they're undoubtedly
good enough to use the C API for Apache as well. .. and they probably
aren't going to be very keen on developing a whole new skill set to do
the same thing in a different manner. (read: lateral shifts don't
benefit anyone)
If anything .. and this isn't taking sides .. but I dare say mod_perl is
more mature than JServ and more tightly integrated into the core of
Apache. I may well be wrong on this account, but that's what my gut is
telling me.
JServ has it's place and mod_perl has it's place .. just don't try to
shove the sqare peg into the round hole - you'll only succeed in pissing
off the peg and offending the hole.
-- dsp
> At 09:13 AM 7/13/99 -0700, you wrote:
> >I am trying to convince other members of my project to
> >replace mod_perl with Apache/Jserv. Currently we
> >have mod_perl and using Perl DBI/DBD to do database
> >connection. What's the advantages of Jserv over
> >mod_perl in terms of performance and functionalities?
> >
> >
> >Yang-Chao
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
