Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-dev@jakarta.apache.org
Sender: jfclere@vtxrm2.bcn.fsc.net
Message-ID: <3BA21BB7.588EC95D@fujitsu-siemens.com>
Date: Fri, 14 Sep 2001 17:01:11 +0200
From: jean-frederic clere <jfrederic.clere@fujitsu-siemens.com>
Reply-To: jfrederic.clere@fujitsu-siemens.com
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: IIS Connector for TC4.0
References: <D84B43C5F94DD511877400609457497C01C9F9@css4.cs>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

GOMEZ Henri wrote:
> 
> >> 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 -
> >
> >Maybe to you, but buddy "Costin" doesn't like it... :)
> 
> No I'm sure Costin like the merge, and I like
> you all comment the following timing :
> 
> 1) Release TC 3.3/4.0
> 
> 2) Start to think on how to merge AJP14/WARP
> 
> 3) Add the AJP14-WARP protocol to mod_jk and mod_webapp (adaptation)
> 
> 4) Add APR to mod_jk and worker concept to mod_webapp

I would do:

 1) Release TC 3.3/4.0
 
 2) Start to think on how to merge AJP14/WARP

 3) APRise mod_jk (Adding in a sense you can have a code with/without it via
configure would be a lot more work).

 4) Add the AJP14-WARP protocol to mod_jk and mod_webapp (adaptation)

 5) Add the worker concept to mod_webapp

Because the WARP protocol part of mod_webapp could be used unchanged (or nearly
unchanged) in mod_jk.