Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 76898 invoked by uid 500); 13 Sep 2001 19:14:06 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 76875 invoked from network); 13 Sep 2001 19:14:06 -0000 Message-ID: From: GOMEZ Henri To: tomcat-dev@jakarta.apache.org Subject: mod_jk using warp protocol ? Date: Thu, 13 Sep 2001 21:14:07 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N What about adding warp protocol to mod_jk and may be adding with functionnalities from ajp14 ? Of course in J-T-C, since mod_jk in J-T must be freezed. ajp14 and warp are very similar, they use the same (it seems) logon system (using md5), and differents protocol encoding but since ajp14 is still experimental, it could be changed in using warp packet system. I've got some questions here : In ajp14, the JkAutoMount was designed to help web-server knows about URL/URI handled by the remote tomcat (examples/*.jsp, examples/servlet/*). JkAutoMount * myworker This allow us to remove the need of configuring these mappings in httpd.conf. More in ajp14, the AutoMount key is the Virtual, if a Virtual section is present in Tomcat we could be sure that a Virtual section in Web-Server will get mappings only for the corresponding Virtual of Tomcat. JkAutoMount myhost1 myworker Did there is the same strategy in mod_webapp ? May be the local Apache Gurus (JF, Ryan) could tell us if we could avoid to set myhost1 in ? The VirtualHostName must be present somewhere in Apache Recs... - Henri Gomez ___[_]____ EMAIL : hgomez@slib.fr (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6