for http is only simple get to backend... and on the backend you must provide a responde this check (ex:statics file)...
you can define how many ping after how it consider the backend dead...
and how many seconds between ping...
From: Jim Jagielski [mailto:[EMAIL PROTECTED]
To: dev@httpd.apache.org
Sent: Mon, 19 Jun 2006 23:02:11 +0200
Subject: [EMAIL PROTECTED] Re: mod_proxy_balancer/mod_proxy_ajp TODO
Ruediger Pluem wrote:
>
> +1. Just one thought: I think it would be useful to have this 'health check'
> approach somewhat generic so that we can implement the call to it inside mod_proxy
> and its connection pooling itself (e.g. with providers supplied by schema
> handlers / modules). For AJP this would be CPING/CPONG of course and
> mod_proxy itself could offer a generic TCP connection 'health check' provider that simply
> checks the status of a TCP connection as far as this is possible without
> reading or writing data. This would be a very generic provider. Other protocol
> handlers could define other (better) protocol specific providers and
> just plug them in.
>
Agreed. Making a generic hearbeat interface that could vary depending
on the actual protocol would be v. cool. So for AJP, CPING/CPONG,
for HTTP some sort of generic TRACE (or HEAD)...
--
===========================================================================
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
"If you can dodge a wrench, you can dodge a ball."
