At 12:34 PM 6/11/2005, Jeff Trawick wrote: >> I like the idea of toggling columns, I'd make it more like >> columns=pid,tid,ss,m,req to allow for abbreviated displays. > >columns= with column names like that works for me > >columns=all displays everything (may change layout in the future) >default list for columns is whatever we display now
I like columns=* personally :) Less ambiguous if we decree all columns can be toggled (especially if we allow modules to extend them). Perhaps +/- syntax? Painful in code, but easier for the user (?columns=+tid). +/- wouldn't reorder the columns from their default, while explicit lists would? >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=xml implies that you get just the >extendedstatus table and absolutely nothing else I'd want the mode (xml v.s. html) to be toggled with a different option flag. The only reason for combining xml and columns would be some synthesized columns that require extra cpu, and the user knows exactly what they will use. I don't know of many computationally intensive columns, but if we later let this become extensible, I can see where that would become a potential issue. > > 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 I'll scratch :) If you have a first draft, I'll follow, otherwise I'd steal code from mod_autoindex to start with. Of course, this would be trivial with libapreq in the core, and would support using POST :) Bill
