In our particular case, jserv is more attractive because the memory
footprint of the server processes is much smaller, meaning a single head-end
can handle as much as 6 or 7 times as many connections. This means less
head-ends are required to match our traffic load, which saves the company
money, etc.
This realization isn't specific to ApacheJserv but servlets in general.
However because we were already using apache+mod_perl it makes sense to go
with ApacheJserv.
Also, we are using apache/linux for web server and sql server 6.5/NT for
database. We had to choose SQL6.5 because no DBI driver was available for
SQL7.0 - using JDBC we were easily able to acquire a level 4 driver that
accomodates both 6.5 and 7.0.
-mdf
+-----Original Message-----
+From: Yang-Chao Lin [mailto:[EMAIL PROTECTED]]
+Sent: Tuesday, July 13, 1999 9:14 AM
+To: Java Apache Users
+Subject: Jserv v.s. mod_perl
+
+
+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]
+
--
--------------------------------------------------------------
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]
