-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 8/23/2011 4:59 PM, Mark Thomas wrote:
> [The NIO code is ]not really [any less robust]. The code between
> all the connectors is getting more similar as I reduce the
> duplication. That should mean fewer bugs/inconsistencies and
> simpler fix
On 23/08/2011 21:50, Christopher Schultz wrote:
> Mark,
>
> On 8/23/2011 4:43 PM, Mark Thomas wrote:
>> On 23/08/2011 21:37, Christopher Schultz wrote:
>>> But, since I'm using AJP, there is a one-to-one relationship
>>> between request processors at the httpd level and in Tomcat, so
>>> being a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 8/23/2011 4:43 PM, Mark Thomas wrote:
> On 23/08/2011 21:37, Christopher Schultz wrote:
>> But, since I'm using AJP, there is a one-to-one relationship
>> between request processors at the httpd level and in Tomcat, so
>> being able to hand
On 23/08/2011 21:37, Christopher Schultz wrote:
> All,
>
> I've been using Tomcat fronted by Apache httpd (terminating SSL I
> might add) for years and I've never given any thought to which
> flavor of AJP connector I've been using. We don't build APR as part
> of our standard build process and i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I've been using Tomcat fronted by Apache httpd (terminating SSL I
might add) for years and I've never given any thought to which flavor
of AJP connector I've been using. We don't build APR as part of our
standard build process and it's unclear fr
