doh! load-balancing of course...
I don't know, I'm a stickler for the old "do one thing, do it well",
tomcat rocks at serving dynamic java, apache rocks at being internet
facing serving static & CGI. the jk connector is good & solid, so I'm
happy to keep everything separate and only have tomcat serving dynamic
pages. plus that way if you ever run into scalability problems you have
the infrastructure to scale right there!
* Matthew Kerle
* * IT Consultant *
* Canberra, Australia*
Mobile: +61404 096 863
Email: Matthew Kerle <mailto:[EMAIL PROTECTED]>
Web: Matthew Kerle <http://threebrightlights.blogspot.com/>
Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matt,
Matthew Kerle wrote:
Apart from integration into a larger site or static content, when would
you put httpd in front of tomcat?
This might count as "integrating into a larger site", but I use Apache
httpd to front multiple instances of Tomcat through a single port number
(by mapping webapps individually through mod_jk). This allows me to
start and stop a single webapp, upgrade the JVM and/or Tomcat running
it, and then bring it back up again without disturbing the other
applications.
- -chris
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
