Re: [PATCH] 2.0 mod_status, 1st try

[Ben Laurie <be...@algroup.co.uk>]

Manoj Kasichainula wrote:
> 
> On Wed, Aug 25, 1999 at 09:42:17AM -0700, Dean Gaudet wrote:
> > on first glance this looks like a great start... but i'm wondering if what
> > you might want to do is have a function:
> >
> > int register_status_column(const char *column_name);
> 
> I like it. I was only planning to support this for protocol modules,
> but I guess there's no real reason why this can't be done for the
> others as well.
> 
> The only problem is that every module's status column then has to be
> available for every connection, because the question of whether a
> module is "used" or not during a connection is much more iffy when we
> don't limit ourselves to protocol modules.
> 
> > hmm... but you need a way to set the values.
> 
> This would be needed even with support for just the protocol module.
> 
> How about an MPM-provided equivalent to ap_update_child_status()? This
> would be slightly different though; it'd be called by any module
> maintaining a status column, whenever it wants to update a field.
> Then, we put control over how and when this information is passed in
> the hands of the MPM where it belongs.

Or, add a hook for status column values, and call it at the appropriate
moments, with the connection as the parameter. Give it a struct to fill
in, with column name and value. Simple. You still need to register them
as Dean suggested so you can get the title bar right.

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi