Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 43292 invoked by uid 500); 21 Mar 2001 22:21:29 -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 43150 invoked from network); 21 Mar 2001 22:21:20 -0000 Message-ID: <361024C34A6DD2118689006097AE2B4D0102C8D8@css4.cs> From: GOMEZ Henri To: tomcat-dev@jakarta.apache.org Subject: RE: mod_webapp status? Date: Wed, 21 Mar 2001 23:21:19 +0100 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'm rewriting it using APR... As we speak... >> >> Pier (under the snow in Dublin) >> > APR is a great piece of code but it will restrict Tomcat to have only one front-end, Apache Web Server. A solution will be to add ajp13 support to Tomcat 4.0. I saw 3 main advantages : 1) Tomcat 4.0 could be used with NES, IIS, Apache and you'll be able to replace Tomcat 3.2.x by Tomcat 4.0 2) Less pression, since a working a stable Apache connector is really needed for the TC 4.0 startup 3) We could see how to use mod_webapp in TC 3.3 Weather announce: Chambery is under rain, but no snow yet in town ;-)