Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <46A97A4D.1070209@hanik.com>
Date: Thu, 26 Jul 2007 22:53:33 -0600
From: Filip Hanik - Dev Lists <devlists@hanik.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: Tomcat connectors
References: <46A520DB.7030708@apache.org>
 <D9EB7C2D-0F31-44AD-B53A-4F4BBCAA0C9F@gmail.com>
 <46A78BCC.6050208@apache.org>
In-Reply-To: <46A78BCC.6050208@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jeff Genender wrote:
> Ok I added a whole bunch of new connectors in the o.a.g.t.connectors
> package.
>
> I am still working on APR - more notes to follow on this as its a little
> squirly since the Tomcat Connector somewhat "chooses" this automatically
> based on the existence of a native libraries.  For the console we may
> wish to do a check on whether the native libs exist, and if so, present
> the APR connector.  More on this in another email.
>   
not really, it works the same as the NIO connector selection, in 
server.xml if
protocol="HTTP/1.1" and the java.library.path contains the TC native 
library (tcnative.dll or libtcnative.so)
then APR is selected.
however, the protocol attribute also takes a complete class name, like

protocol="org.apache.coyote.http11.Http11Protocol" <-- java blocking 
connector
protocol="org.apache.coyote.http11.Http11NioProtocol" <-- java non 
blocking connector
protocol="org.apache.coyote.http11.Http11AprProtocol" <-- APR connector

so there is no need to dabble with the auto select, personally I don't 
think its very usable feature, since the APR SSL connector has different 
attributes than the Java SSL connector and the auto select wouldn't work 
in that scenario anyway.

Filip

> Here are the connectors we care about at the moment...
>
> AJP13ConnectorGBean - Implements AJP
> Http11ConnectorGBean - Implements blocking Http connector
> Https11ConnectorGBean  - Implements blocking Https connector
> Http11NIOConnectorGBean - Implements non-blocking Http connector
> Https11NIOConnectorGBean - Implements non-blocking Https connector
>
> I have not wired them into the container and other GBeans yet...I want
> to clena them up and get any feedback before making the switch since
> this obviously will impact the console upon wiring them in.
>
> As a side note...I am not using any references to the WebManager or
> other interfaces we used that hooked into the console.  We can re-add
> those if those are deemed necessary.
>
> Jeff
>
> Paul McMahan wrote:
>   
>> I agree NIO support would be great to have in 2.0, especially since its
>> required for comet.
>>
>> Best wishes,
>> Paul
>>
>> On Jul 23, 2007, at 2:42 PM, Jeff Genender wrote:
>>
>>     
>>> Hi,
>>>
>>> I was going through some JIRAs and the Geronimo2.0 source and noticed it
>>> will be difficult at best to get the NIO connector and setting
>>> attributes on the APR connector for Tomcat due to its current
>>> implementation.  I really think the ability to use these 2 connectors is
>>> very important for the 2.0 release and I would like to put these in.  If
>>> there are no objections, I would like this to be a part of the 2.0
>>> release.
>>>
>>> Jeff
>>>       
>
>
>