Hey David,

Don't know if you remember me from GTE NMO or not...  Hope all's well with
you and BEST.

Apache supports HTTP 1.1 whereas the last I heard, Tomcat was only HTTP 1.0,
so each request comes over it's own connection rather than sharing as with
Apache.  This means that Apache is still a good idea because it serves image
files a bit more nicely along with the JSP generated page, and most web
sites have a fair amount of image files.

Apache is generally more robust and secure having been tested in production
environments for a long time, and it will allow you to serve up other kinds
of files nicely in the future (PHP, Perl, Python, CGI, etc.), and I'm sure
it's SSL is must faster because it's native C code.  Tomcat probably uses
JSSE, and even Sun doesn't claim it's a production-quality SSL package,
though it seems to work well enough for me (I use it for SOAP calls from the
client side to our web service).

Lastly, I use Apache+modSSL to run on a front-end server with the Tomcat
system on a different computer (using NAT and a firewall to limit
connections to the app server as through the connector ports).  This
provides some added security because Tomcat can run on a private network
instead of the publicly accessible web server.

David
---------------------------------------------
David A. E. Wall
Chief Software Architect
Yozons, Inc.
724 17th Avenue
Kirkland, WA 98033 USA
Tel 425.822.4465    [EMAIL PROTECTED]
Fax 425.827.9415    www.yozons.com


----- Original Message -----
From: "David M. Karr" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 01, 2001 6:20 PM
Subject: Any reason to use Apache w/ Tomcat for webapp with all dynamic web
pages?


> If you're committed to a project where virtually all of the pages will be
> dynamically generated, through JSP most likely, and you're committed to
using
> Tomcat, is there ANY good reason to use Apache, in addition to Tomcat?
>
> I surveyed the FAQ, and I didn't notice this question being specifically
> addressed.  AFAIU, Apache is good for serving static pages or resources.
If
> you're only serving dynamic content, it only serves to complicate the
> deployment, and serves no useful purpose.
>
> Can anyone give me any opposing viewpoint, assuming a dynamic webapp with
> Tomcat?
>
> --
> ===================================================================
> David M. Karr          ; Best Consulting
> [EMAIL PROTECTED]   ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)

Reply via email to