You can just run Tomcat on port 80 if that's what you want.

Many people have many different reasons for using Apache:

- Apache doesn't run as root on port 80
- Apache has other capabilities (mod_rewrite, etc.)
- Apache is "better" at serving static content...for a heavy traffic site
this can make a difference ("better" is relative to your webapp)
- there are legacy requirements: PHP, perl, etc.
- You want to use Apache's access control (.htaccess)
- you want to load-balance to multiple Tomcats
- you have proprietary Apache DSO that you have to support

...and on and on and on.

Basically, it comes down to this:  If your webapp works fine with Tomcat
stand-alone, and you don't mind running Tomcat as root on port 80, then
change CoyoteConnector to listen on port 80 instead of 8080 and call it
good.  If your webapp can benefit from putting the task of serving static
content onto Apache's shoulders, you don't want to run Tomcat as root on
port 80, you want to load-balance, or you have a need for any one of
Apache's many capabilities, use Apache + connector + Tomcat.

John

> -----Original Message-----
> From: Mark O'Neil [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 11:29 AM
> To: Tomcat Users List
> Subject: JK vs. Standalone?
> 
> 
> Hello,
> 
> I may be a bit confused, but here goes anyway:
> 
> My understanding is that JK 'binds' tomcat to apache so that 
> instead of 
> running a servlet or jsp via the Tomcat port "http://my-
> host:8080/my-servlet" you can run it via apache directly "http://my-
> host/my-servlet" - correct?
> 
> The question then is: what are the determining factors for 
> implementing 
> JK in a production system? Specifically why would I and to 
> what benefit? 
> I have a feeling it has to do with combining the otherwise different 
> document roots and file management(?).
> 
> Insights please.
> 
> regards,
> -m
> 
> 
> --
> 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]>

Reply via email to