>I thought the idea of warp/webapp was that it was to support
>servlet api 2.3
>and ajp/jk couldn't eaily be modified to support the new specs.
What's the supposed features in 2.3 that ajp/jk couldn't support ?
At least there will be in ajp14/jk the autoconfig (ie list of
URL/URI handled ) =>
/examples/servlet/*
/examples/*.jsp
/examples/*.xml
>
>Dave
>[EMAIL PROTECTED]
>
>
>>From: kevin seguin <[EMAIL PROTECTED]>
>>Reply-To: [EMAIL PROTECTED]
>>To: [EMAIL PROTECTED]
>>Subject: Re: connector status in tomcat 4
>>Date: Mon, 28 May 2001 09:52:43 -0500
>>
>> >
>> > Ok, so which one would you say should has highest priority?
>> >
>>
>>that probably depends on who you ask ;-)
>>
>> > Having a quick look at the CVS repository I see
>>jakarta-tomcat-connectors,
>> > which contains the jk-park, and in jakarta-tomcat I see
>the warp/webapp.
>>Is
>> > this right? Won't ajp13/jk be included in tc4? Is it going to be
>>replaced by
>> > warp/webapp?
>> >
>>
>>jakarta-tomcat-connectors (jtc) is a new module where connectors like
>>ajp, warp/webapp, etc. should live. the idea is that the
>core parts of
>>connectors should be container-agnostic. only the request/response
>>adapters should know about containers.
>>
>>ajp/jk will not be "included" in tc4, but it will support tc4 -- there
>>will be (is) an ajp13 connector for tc 4 (it's is a work in progress).
>>going forward, ajp connectors for tc 3, tc 4, and maybe other
>containers
>>will live in jtc.
>>
>>warp/webapp will not replace ajp/jk, but it will give you another
>>choice. you'll be free to make the decision yourself as to what
>>connector you want to use.
>>
>> > // Erik
>> >
>> > > -----Original Message-----
>> > > From: kevin seguin [mailto:[EMAIL PROTECTED]]
>> > > Sent: Monday, May 28, 2001 3:05 PM
>> > > To: [EMAIL PROTECTED]
>> > > Subject: Re: connector status in tomcat 4
>> > >
>> > >
>> > > GOMEZ Henri wrote:
>> > > >
>> > > > >My question is what the status is on the apache connector in
>> > > > >tomcat 4. I've
>> > > > >been testing Jakarta 4 in standalone mode and is very pleased
>> > > > >with it, but
>> > > > >we can't run it like that once we release the system for all
>> > > > >our students..
>> > > > >;)
>> > > >
>> > > > There is actually 2 connectors for Apache Tomcat 4.0 :
>> > > >
>> > > > - warp/webapp : Developped specifically for TC 4.0 have
>> > > > autoconfig stuff but lack load-balancing or IIS/NES support
>> > > >
>> > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
>> > > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
>> > > > (will came in ajp14) but have load-balancing and IIS/NES
>> > > > support.
>> > > >
>> > >
>> > > er... the load-balancing doesn't work yet for tc 4 --
>the java side
>>of
>> > > it hasn't been done yet. it shouldn't be too hard to do
>though :) i
>> > > think it's just a matter of figuring out what to do with
>jvmRoute on
>>the
>> > > java side (set a cookie??).
>> > >
>> > > > Your contribution must match your need !)
>
>_______________________________________________________________
>__________
>Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.
