Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 61439 invoked by uid 500); 15 May 2001 16:16:41 -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 61165 invoked from network); 15 May 2001 16:16:21 -0000 Message-ID: <361024C34A6DD2118689006097AE2B4D0102CF7A@css4.cs> From: GOMEZ Henri To: tomcat-dev@jakarta.apache.org Subject: RE: Trying New Connectors Build Stuff Date: Tue, 15 May 2001 18:16:16 +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: h31.sny.collab.net 1.6.2 0/1000/N >I ask mostly because I've put a lot of effort into cleaning up and >documenting that code, and I hope that it is now much more >workable. Your documentation is a great help in extending the jk in jakarta-tomcat-connectors to add ajp14 support. I'll try to also comments my code to help it being understoud by users and commiters, and of course code review. Just take a look in jakarta-tomcat-connectors/jk/src/native... >If you >still find it difficult to read/understand, I'd love to know >how/where. I >still hold out hope that at some point in the future the mod_webapp >protocoal (warp?) could be supported by mod_jk, so there would >be only one C >code base to support. mod_webapp is too different from mod_jk, and there will be 2 native code base to support, to avoid that : - Someone implements the warp protocol in mod_jk - Someone implements ajp12 or ajp13 in mod_webapp