Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 85098 invoked by uid 500); 2 Oct 2001 02:45:41 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 85087 invoked from network); 2 Oct 2001 02:45:40 -0000 Message-ID: <005201c14aec$54649620$5a2b7ad8@expertrade.com> Reply-To: "David Wall" From: "David Wall" To: , References: <86vghyon20.fsf@earthlink.net> Subject: Re: Any reason to use Apache w/ Tomcat for webapp with all dynamic web pages? Date: Mon, 1 Oct 2001 19:45:42 -0700 Organization: Yozons, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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 dwall@yozons.com Fax 425.827.9415 www.yozons.com ----- Original Message ----- From: "David M. Karr" To: 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 > dmkarr@earthlink.net ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)