Hi! As far as I have heard mod_jk appears to be unstable with apache2 and as you said mod_jk2 is heavily in development. That leaves us with mod_webapp (for now).
>From what I gather from the last posts (especially from Costin who amongst others is developing the mod_jk2 connector), it doesn�t look like as if mod_webapp is really going to be replacing mod_jk in the near future. I can�t imagine them putting so much energy into it if it�s going to get dropped soon! It appears though until there is a stable mod_jk connector for apache2 we will have to use mod_webapp. bye Michael Delamere p.s. Coyote: as far as I know it�s a new HTTP connecor which you can replace with the deafult one. > I'm confused with the state of the connectors available for Apache2/Tomcat > integration. Could someone, please, shed some light on this. The following > is some of what I've read/interpreted from messages on this list: > > mod_jk: Unstable > mod_jk2: Bleeding edge for development purposes only > mod_webapp: Next generation integration module for Apache/Tomcat that will > eventually replace mod_jk's. However, performance hit since even static > pages will have to go through Tomcat before being served by Apache. > > coyote: ??? > > > Thank You, > Anthony > > -- > 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]>
