It always depends on... if the focus is on the servlets (meaning around 70% of the requests are satisfied by your servlets), maybe you want to give a tomcat-only-setup a try. however, if the focus is on static / php / perl-content an less than 50% of the requests are satisfied by servlets, i'd put apache httpd in front and connect to tomcat with mod_jk.
there was one security-issue with mod_jk, however, that was one in the past few years i know of and it was fixed. however, you could also use mod_proxy in conjunction with mod_proxy_ajp to connect to tomcat, however, i'd do it the apache way with mod_jk2. again, serving static / php / perl-content, for performance-reasons apache httpd should be your choice (or maybe squid, but that's a different story) we are running two hardware-loadbalanced servers each having apache-httpd / mod_jk2 / tomcat 55-setup, and it runs like charm. cheers greg -- what's puzzlin' you, is the nature of my game gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
