Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 12380 invoked by uid 500); 14 Sep 2001 08:06: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 12370 invoked from network); 14 Sep 2001 08:06:40 -0000 Message-ID: From: GOMEZ Henri To: tomcat-dev@jakarta.apache.org Subject: RE: IIS Connector for TC4.0 Date: Fri, 14 Sep 2001 10:06:50 +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 >So, IMO, it's a win-win situation... JK can support all >web-servers and all >"old" protocols, it's tested, it works, we just need to make >it able to talk >the new "AJPv14/WARP" protocol and can be used as the "strong" >foundation. >WebApp will talk only "AJPv14/WARP", based on APR, and only >ported to Apache >1.3 and 2.0, when we're happy with it, with the 3.3 implementation of >"AJPv14/WARP", with the new/revised/corrected APR-based API, >we can start >porting all other stuff over, and in 12 years time we can >deprecate the old >one... > >Does it make any sense? Yes - Pier which will became my best friend :)