Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: domain of trawick@gmail.com designates
 64.233.162.193 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=reegUkPcirRhYYrB4M7qiph2fmGDu633D9WnLZ1LTmfkUb7Z7u05Akv2GAs+z6Ohrbu53M0VXaad7V4dxbiyb74b52IhwwL9H27CGBnCgF9Gg9YMHoTHOu0oNtBl160fg9+g7zaVgxRdTtoOTfy4lp2inDGNZfA6VT6dnMh7WPk=
Message-ID: <cc67648e0506111034271c33b6@mail.gmail.com>
Date: Sat, 11 Jun 2005 13:34:27 -0400
From: Jeff Trawick <trawick@gmail.com>
Reply-To: Jeff Trawick <trawick@gmail.com>
To: dev@httpd.apache.org
Subject: Re: displaying thread id in mod_status ExtendedStatus table - how to
 request it?
In-Reply-To: <6.2.1.2.2.20050609111352.06440920@pop3.rowe-clan.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <cc67648e05060903032cea8d80@mail.gmail.com>
	 <6.2.1.2.2.20050609111352.06440920@pop3.rowe-clan.net>

On 6/9/05, William A. Rowe, Jr. <wrowe@rowe-clan.net> wrote:
> At 05:03 AM 6/9/2005, Jeff Trawick wrote:

> >Requre threadid in query argument to see this information?
> >(/server-status/?notable&threadid or something like that)
> >
> Or name the columns?  Better yet, move to an XML output
> (?refresh=3D5&display=3Dxml) which any decent parser can tear apart,
> no matter how we change things in the future?
=20
> I like the idea of toggling columns, I'd make it more like
> columns=3Dpid,tid,ss,m,req to allow for abbreviated displays.

columns=3D with column names like that works for me

columns=3Dall displays everything (may change layout in the future)
default list for columns is whatever we display now

modules need a flag to their status hook to know to implement xml (or
omit if xml is required)...  xml representation needed for everything
else as well...  or display=3Dxml implies that you get just the
extendedstatus table and absolutely nothing else
=20
> One other thing, we should probably contemplate disallowing
> certain fields.  E.g. someone who wanted server-status, but
> didn't want to leak pid/tid or remote IP information might
> want to lock out those fields from being returned.

in due time, if someone is sufficiently itchy