You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2009/03/30 16:25:11 UTC
Re: mod_watchdog API, was Re: svn commit: r759751 - /httpd/httpd/trunk/modules/cluster/mod_heartbeat.c
On Mar 30, 2009, at 5:22 AM, Paul Querna wrote:
> On Mon, Mar 30, 2009 at 10:48 AM, Mladen Turk <mt...@apache.org>
> wrote:
>> Paul Querna wrote:
>>>
>>> On Sun, Mar 29, 2009 at 10:44 PM, Paul Querna <pa...@querna.org>
>>> wrote:
>>>
>>> Inside a MPM that does it natively, just use the registered list of
>>> providers, and implement the same behavoirs as the module.
>>>
>>
>> The problem with mpm is that (IIRC the proposal) it uses
>> the current free resource. However if busy there will be no
>> resources available. So the solution is to dedicate a
>> separate resource for watchdog thread(s). Now, that's a
>> plain duplicate of mod_watchdog copied across the mpms.
>
> fine, disagree with that, but what are your thoughts on switching to
> the provider API?
>
+1 to provider... it's one of the best parts of httpd
Re: mod_watchdog API, was Re: svn commit: r759751 - /httpd/httpd/trunk/modules/cluster/mod_heartbeat.c
Posted by Mladen Turk <mt...@apache.org>.
Jim Jagielski wrote:
>
>>
>> fine, disagree with that, but what are your thoughts on switching to
>> the provider API?
>>
>
> +1 to provider... it's one of the best parts of httpd
>
But it uses the provider already :)
Regards
--
^(TM)