I was just giving you good practice, vs no so good practice.
I take it you disagree. You can load balance Tomcat just fine.
IMO: It's a good practice to try to avoid using Apache. Mostly newbies think that this is required. I am just saying, this is not required or possibly good.
It makes operations and development easier not to have Apache, and my clients have removed it to great sucess. Take it into consideration a word to the wise.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg85780.html
.V
Please don't troll the list. There are all sorts of reasons besides "need CGI" to use Apache. I can think of one right now (load balancing) that would pretty much make using Apache mandatory in many installations.
Instead of bashing people for the software they choose to use, a more helpful response might be to help them use it easily.
John
-----Original Message-----
From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 7:00 AM
To: [EMAIL PROTECTED]
Subject: Apache and Tomcat: a bad practice
Lot's of Apache to Tomcat questions.
In the past, (Hardware sales) people would say you need a html server (Apache) and a jsp server (Tomcat).
Now.... Tomcat can server HTML pages very fast and can do SSL, etc.
There is no reason to maintain and configure in operations communications between the two.
Recomendation: It is *a good practice to deprecate Apache!, and use Tomcat* (or other J2EE, such as Resin) as your only server, SSL and HTML, etc.
The speed is just fine.
There are only a few exceptions, such as you need CGI, but you can save money, time now, but de-instaling Apache and put Tomcat on port 88 and 443.
.V
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
