I used to use TC behind Apache but found that a bit flakey under windows (which was my dev platform), and I found configuring the two servers separately a bit fiddly. So when I started a new project I did a bit of homework on TC standalone, then decided to drop Apache entirely and run TC standalone. No complaints so far, and I've yet to see a convincing case for introducing Apache into the picture (although maybe there are reasons to do this, in different circumstances to mine).
> -----Original Message----- > From: Robert Bateman [mailto:[EMAIL PROTECTED] > Sent: Friday 22 October 2004 17:12 > 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]
