Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Subject: RE: [Slightly OT] Simplifying deployment
From: Robert Bateman <bobbateman@sequoiallc.com>
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
In-Reply-To: <9C5166762F311146951505C6790A9CF80229C480@US-VS1.corp.mpi.com>
References: <9C5166762F311146951505C6790A9CF80229C480@US-VS1.corp.mpi.com>
Content-Type: text/plain
Message-Id: <1098463294.8091.7.camel@development.sequoiallc.com>
Mime-Version: 1.0
Date: Fri, 22 Oct 2004 12:41:34 -0400
Content-Transfer-Encoding: 7bit

THANKS Chad and Yoav!

Very good information.  I will look elsewhere for performance
improvements (possibly squid...)

Bob

On Fri, 2004-10-22 at 12:24, Shapira, Yoav wrote:
> Hi,
> Yup, Chad's right.  About the worst thing you can do is add complexity
> because you *think* it might be better.
> 
> You do see a lot of connector-related traffic on this list.  That's
> because connector configuration is not easy.  The specifics greatly
> depend on which connector version, which tomcat version, which front-end
> (Apache httpd, IIS, others), and what environment you're using.  And for
> many systems, the initial effort as well as the long-term maintenance
> costs are simply not worth it.  For many other systems, the performance
> gain is not worth it.
> 
> So if you really have an itch to scratch, make sure you set up a proper
> test server and benchmark your app to see if performance is really
> gained.  Since your app is all Java (no PHP, CGI, etc.), you have no
> other argument for putting a front-end with Tomcat.  Only if performance
> gains are substantial, and you still feel the added complexity/fragility
> is worth it, then I'd go ahead to modify your production setup.
> 
> Yoav Shapira http://www.yoavshapira.com
>  
> 
> >-----Original Message-----
> >From: Chad Maniccia [mailto:cmaniccia@majorbrand.com]
> >Sent: Friday, October 22, 2004 12:19 PM
> >To: Tomcat Users List
> >Subject: RE: [Slightly OT] Simplifying deployment
> >
> >I would keep it simple less things to hack, break, update, etc..
> >Also I remember reading in tomcat's documentation that it serves static
> >content almost or just as fast.
> >
> >
> >-----Original Message-----
> >From: Robert Bateman [mailto:bobbateman@sequoiallc.com]
> >Sent: Friday, October 22, 2004 11:12 AM
> >To: Tomcat Users List
> >Subject: [Slightly OT] Simplifying deployment
> >
> >I have an application that I've developed that run strictly on Tomcat.
> >
> >I've noticed a lot of traffic on this list talking about using Apache
> >httpd to serve up static content and using mod_jk to have httpd talk to
> >Tomcat to serve up JSP traffic.  And all of that got me thinking about
> >doing the same thing - sepecially since httpd is probably faster at
> >displaying static content....
> >
> >But I'm left with a question:  My application is delivered to my TC
> >instance as a .war file.  It seems to me that I'd have to break out the
> >static content into something else in order for httpd to be able to
> >serve that content.  Is that the best way to accomplish this?  Or is
> >there something better that I can do on a *nix installation?
> >
> >
> >Thanks much!
> >
> >Bob
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 
> 
> 
> 
> This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged.  This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender.  Thank you.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org