This comes up a lot, and the answer, unfortunately, is "do what works for you in your situation".
"Slower" is relative, "best" is relative. Test your app with an estimated load using Tomcat stand-alone, if that works for you, you should be good to go. Using Apache can be a complex task, and it may not be worth the additional administration headache. The main reasons for running Apache with Tomcat are not wanting to run Tomcat as root on port 80, using Apache + JK/JK2 to load-balance to several Tomcats, and taking advantage of other Apache features like CGI/PHP, or modules like mod_rewrite. John > -----Original Message----- > From: Andreas Hucks [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 06, 2002 7:35 AM > To: list: tomcat > Subject: Where to place static content? Tomcat/Apache > > > Hi, > > I am just starting with the Tomcat/Apache combo, so this is a > rather basic > question: > With larger projects, is it better to place the static > content with the > webapp (being able to distribute it inside the .war) or to > map just the > servlets to Tomcat and have the rest served by Apache (better > performance?) > Is Tomcat slower than Apache serving static files? Is it worth the > inconvenience of not having it all in one place? > > Not that it matters right now (it's not a production environment, of > course), just being curious about "best practice". > > Andreas > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
