On Aug 6, 2008, at 5:16 PM, Akins, Brian wrote:
On 8/4/08 3:41 PM, Jim Jagielski [EMAIL PROTECTED] wrote:
*grin*
I've always wondered what usefulness
ap_run_monitor(p)
FWIW, we use the monitor hook all the time...
The usefulness of being passed just a pool is what I
was
Paul Querna wrote:
Mladen Turk wrote:
Comments, other ideas?
I would prefer to not add a separate 'dedicated' thread, but just 'use'
a worker thread, when it is about to idle instead. When you are about
to go into the idle wait, check if there are any timed tasks that need
to execute
Mladen Turk wrote:
IMO this should be just like any listener thread, so that logic
can be decoupled from the main worker logic serving requests.
+1.
I looked at the monitor hook, which I understand to run every 10 seconds
or so, though that may not be convenient for everybody. The monitor
On 8/4/08 3:41 PM, Jim Jagielski [EMAIL PROTECTED] wrote:
*grin*
I've always wondered what usefulness
ap_run_monitor(p)
FWIW, we use the monitor hook all the time... Most of our stuff uses some
shared memory and the monitor hook in parent, but I have considered hacking
something
Hi,
Right now any event happening in mpm child process
is per request based. As an example I'll give
mod_proxy and its connection pool. The connection_pool
maintenance happens only when a request comes in which
is fine for a frequently accessed server. If there
is no request for a long time the
On 8/4/08 12:59 PM, Mladen Turk [EMAIL PROTECTED] wrote:
mod_balancer decaying (averaging) the transferred statistics,
so that node-up/recovery doesn't consume all the load.
mod_proxy_ajp sending ping/pong at regular intervals (detecting
node failure before
Mladen Turk wrote:
Comments, other ideas?
I would prefer to not add a separate 'dedicated' thread, but just 'use'
a worker thread, when it is about to idle instead. When you are about
to go into the idle wait, check if there are any timed tasks that need
to execute soon, and run that
On Aug 4, 2008, at 1:57 PM, Paul Querna wrote:
Mladen Turk wrote:
Comments, other ideas?
I would prefer to not add a separate 'dedicated' thread, but just
'use' a worker thread, when it is about to idle instead. When you
are about to go into the idle wait, check if there are any timed
On Aug 4, 2008, at 1:25 PM, Akins, Brian wrote:
On 8/4/08 12:59 PM, Mladen Turk [EMAIL PROTECTED] wrote:
mod_balancer decaying (averaging) the transferred statistics,
so that node-up/recovery doesn't consume all the load.
mod_proxy_ajp sending ping/pong at regular intervals
