svn co http://svn.apache.org/repos/asf/tomcat/trunk
On 02/25/2010 01:48 PM, Filip Hanik - Dev Lists wrote:
On 02/25/2010 01:26 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James,
On 2/25/2010 12:47 AM, James Roper wrote:
Is there anyone on this list with a d
On 02/25/2010 01:26 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James,
On 2/25/2010 12:47 AM, James Roper wrote:
Is there anyone on this list with a detailed knowledge of the NIO
Connector?
In spite of his terse reply, Filip is, I believe, quite fami
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James,
On 2/25/2010 12:47 AM, James Roper wrote:
> Is there anyone on this list with a detailed knowledge of the NIO
> Connector?
In spite of his terse reply, Filip is, I believe, quite familiar with
that code. Would you consider writing a patch and
On 02/23/2010 10:09 PM, James Roper wrote:
Hi,
I'm trying to understand how the Tomcat 6.0 NIO connector handles the
various limit attributes in the configuration, particularly in regards
to comet requests. I've had a look at the source code, and I think I
understand, but I'd like to confirm
Chris,
Thankyou for your comments, it's reassuring to have my logic validated.
Is there anyone on this list with a detailed knowledge of the NIO
Connector? Maybe I should post to the developers list? My reason for
asking these questions is that my company is about to deploy a comet
solutio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James,
On 2/24/2010 12:09 AM, James Roper wrote:
> The acceptCount works just like it does on the other processors, it gets
> passed to the ServerSocket as the backlog parameter. This limit will be
> reached if the acceptor thread(s) aren't able to a
Hi,
I'm trying to understand how the Tomcat 6.0 NIO connector handles the
various limit attributes in the configuration, particularly in regards
to comet requests. I've had a look at the source code, and I think I
understand, but I'd like to confirm my understanding, and also ask some
furthe
