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:[EMAIL PROTECTED]
>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:[EMAIL PROTECTED]
>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: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to