On Sat, 26 Feb 2005 22:32:22 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > +1 from me for the general idea. This could be be very helpful for > administrators/operators to trace problems of hung requests.
Thanks for taking the time to comment. I think a lot of people would benefit from having more concrete facts in hand (easily) when there are web server issues. > > As this > creates more overhead to the request processing (although I think not too > much for me personally) there should be a directive for turning this on/off > like ExtendedStatus. In the patch, it is switched on and off via ExtendedStatus. And the intention was to require a configure option such as --enable-track-request-phase to even allow the capability. I'll be interested in other opinions on such questions, such as * should the capability even be in Apache * should the capability be available by default, or made available only by configure-time option * should the capability be controlled merely by ExtendedStatus on/off, or by an additional value for ExtendedStatus, or by a independent directive > In a second step it would be great to see this > implemented > in a more extensible way such that modules would be able to add their own > phases to this list. e.g there could be an API call like ap_add_phase which > would > add a string to the phase_names array during the configuration phase of a > modul > and would return the index in the array for later use in the > AP_SET_REQUEST_PHASE > macro via the module. That could be nice. I'm a little concerned about using the same mechanism for information maintained by core Apache (not as granular but 99.9% reliable) as well as information maintained by arbitrary modules (more granular but not necessarily reliable), particularly if some save-state/restore-state operation is required as the module enters/leaves its own custom phase. Modules currently can save whatever state they want on their own and implement a mod_status hook to format it appropriately in their own section of the display, but having a scoreboard field and a column in the output table would make that much easier.
