Hmm I woudl have thought otherwise, since after
reading the protocol it seems specificly designed
to support keeping connection alive.
That a sender would keep a pool of available
connections and when a hit comes in get one
which is already connected, and push the request
out, and the
Peter Kennard wrote:
Hmm I woudl have thought otherwise, since after reading the protocol it
seems specificly designed to support keeping connection alive.
That a sender would keep a pool of available connections and when a
hit comes in get one which is already connected, and push the request
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Is APR worth it (for me?)
However, the APR description page suggests that scalability
is improved through the use of socket-polling
The scalability is improved due to not having to keep a thread around
for each persistent HTTP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Is APR worth it (for me?)
However, the APR description page suggests that scalability
is improved through the use of socket-polling
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rémy,
Rémy Maucherat wrote:
The scalability improvement is twofold for AJP:
- when running many Apache frontend servers (each with a sizeable
number of workers), Tomcat would need a huge amount of AJP worker
threads with the java.io connector
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Is APR worth it (for me?)
Makes sense. So, instead of a Java thread waiting in every single ajp
connection, you're using one native listener thread waiting on a
select(), right? It's sad that you can't do this in Java :(
You
Doesn't AJP multiplex traffic, that is queued
up requests are serialized through one
connection that remains connected and it switches
between servlets on the receiving end? and recycles the execution thread?
At 19:19 3/7/2007, you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rémy,
Peter Kennard wrote:
Doesn't AJP multiplex traffic, that is queued up requests are
serialized through one connection that remains connected and it
switches between servlets on the receiving end? and recycles the
execution thread?
No multiplexing on connections.
Regards,
Rainer
At 19:19
Christopher Schultz [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Is APR worth it (for me?)
However, the APR description page
