httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: [PATCH] 2.0 mod_status, 1st try
Date Wed, 25 Aug 1999 16:42:17 GMT
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); 

which registers a column... has to be called during config.  The integer
returned would be used as an index into an array of char * for the status
values...

this eliminates the mpm/protocol-specific stuff -- any module could
register a column.

hmm... but you need a way to set the values.

hmm.

your call :)

Dean

On Wed, 25 Aug 1999, Manoj Kasichainula wrote:

> There are two attachments: a patch to the Apache core + mpmt_pthread
> MPM to support a mod_status API, and a new mod_status.c.
> 
> This illustrates passing basic information from the server to
> mod_status, and support for MPM-specific table columns (in this case,
> pid and thread ID). Adding some actual useful information should be
> easy enough with this infrastructure.
> 
> I haven't decided whether to use shared memory or pipes to implement
> this support for dexter. Since we're already using the scoreboard for
> the pthread MPM, I'm leaning towards using pipes on dexter for
> variety and experimental value.
> 
> Support for protocol-specific data isn't all there yet. To get there,
> we need:
> - protocol identitiers easily available for connections.
> - registration of protocol-specific table headings
> - querying the protocol module for information on a list of
>   connections
> 
> I don't think this will be too hard, though
> 
> Comments? I'm especially looking for thoughts on the API exported for
> use by MPMs and status modules. The current one is not perfect by any
> means.
> 
> Manoj
> 

Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message