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]>
- JK2 & workers2 vs. jk & workers??? chris schild
- Re: JK2 & workers2 vs. jk & workers??? chris schild
- RE: JK2 & workers2 vs. jk & workers??? Turner, John
- Re: JK2 & workers2 vs. jk & workers??? chris schild
- Re: JK2 & workers2 vs. jk & workers??? Robert L Sowders
- RE: JK2 & workers2 vs. jk & workers??? Turner, John
- Mark O'Neil
