Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 7420 invoked by uid 6000); 4 Feb 1999 01:35:47 -0000 Received: (qmail 7407 invoked from network); 4 Feb 1999 01:35:45 -0000 Received: from smtp.lerdorf.on.ca (HELO sunlab.bellglobal.com) (199.243.250.75) by taz.hyperreal.org with SMTP; 4 Feb 1999 01:35:45 -0000 Received: from collective.lerdorf.on.ca (collective.lerdorf.on.ca [207.164.141.23]) by sunlab.bellglobal.com (8.9.1/8.8.8) with ESMTP id UAA07015 for ; Wed, 3 Feb 1999 20:37:36 -0500 (EST) Date: Wed, 3 Feb 1999 20:35:35 -0500 (Eastern Standard Time) From: Rasmus Lerdorf To: new-httpd@apache.org Subject: Re: mod_status.c In-Reply-To: Message-ID: X-X-Sender: rasmus@imap3.bellglobal.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org > > > Maybe we need an API so people can write their favourite mod_status page > > > style templates :-) Sounds like a job for PHP. > > > > Although I think making the mod_status page pretty is a rather useless > > thing to do, the idea of somehow making the information on it available to > > a module is interesting. > > Committing to make the scoreboard portable, and the interface public is > not at all a good idea. > > Contrast the old-style ps which mucked around in /dev/kmem, and the newer > styles which use /proc. It's pretty much the same problem. But a couple of access functions would take care of that. ap_fetch_scoreboard_data() that returned a struct * to the data, for example. -Rasmus