Well, ya I know this. But you could still have apache do a re-direct to tomcat on whatever port it's lisening on (say 8080) and get the same result. My own personal opinion is mod_webapp is cleaner but I'm under some pressue to say WHY it's better. Can't really think of any good reasons really.
Dave -----Original Message----- From: Brian Adams [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 31, 2002 3:23 PM To: 'Tomcat Users List' Subject: RE: why use mod_webapp? same port! port 80 is http (apache) tomcat would then have to run alone on another machine or Virtual IP. the beauty is that we can now SSI jsp/servlet in html and you never bounce to another port or have to add DNS entrees... just a few reasons, you'll get more and better explained. B -----Original Message----- From: Dave North [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 31, 2002 2:21 PM To: [EMAIL PROTECTED] Subject: why use mod_webapp? Hi Folks, I'm already using mod_webapp for handling my tomcat traffic via apache. My question from a guy here is why do we do this and not just create a simple re-direct page? ie. create a directory with a 1 line HTML page in it that re-directs to the tomcat HTTP server. Are there other advantages to using the WARP connector? Thanks Dave Dave North SIGNIANT Inc. Trusted Data Transfer Services www.signiant.com Phone: 613-761-3623 Fax: 613-761-3629 EMail: [EMAIL PROTECTED] -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>