Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-dev@jakarta.apache.org
Message-ID: <D84B43C5F94DD511877400609457497C01BBC1@css4.cs>
From: GOMEZ Henri <hgomez@slib.fr>
To: tomcat-dev@jakarta.apache.org
Subject: RE: connector status in tomcat 4
Date: Tue, 29 May 2001 10:04:50 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

>Ok, another question then.

Please,

>What is it that the connector has to be able to do? Is it 
>sufficient if it
>simply can forward the HTTP request to tomcat or does it need 
>to play around
>with it? I guess it must do something or the disscusion on ajp13/jk and
>warp/webapp wouldn't be.

The web-server connector forward request to tomcat and add some 
information, like the SESSION-COOKIES. In return the tomcat add
a var, jvmroute, which is used in load-balancing config to be sure
that the same tomcat will serve the next queries for that session.

The connector use a simple protocol, ajp12/13/14, to forward the
request. You may imagine a web-connector forwarding the request 
using HTTP protocol, but this one is more complex to handle.
 
>// Erik
>
>> -----Original Message-----
>> From: kevin seguin [mailto:seguin@motive.com]
>> Sent: Monday, May 28, 2001 5:47 PM
>> To: tomcat-dev@jakarta.apache.org
>> Subject: Re: connector status in tomcat 4
>>
>> for example, in my case, currently all i care about is being able to
>> forward requests based on uri from iis and netscape to 
>tomcat.  so, for
>> me, ajp does what i need it to, while warp/webapp currently 
>does not (no
>> iis/netscape support yet).  hence, i would pick ajp.
>>
>> now, i'm not saying one is better than the other.  i'm just 
>saying that
>> one might be better than the other in certain circumstances, 
>and now you
>> have a choice.
>>
>