tally of interested parties for tracking active module in 1.3.x, 2.0.x

[Jeff Trawick <tr...@gmail.com>]

In the very short term I'll have something working with the web
servers I help support which are based on 1.3.x and 2.0.x.  I have no
time to waste trying to DTRT with respect to Apache users if there is
no developer interest.  If there is developer interest, I'm happy to
work towards a common solution if it can move fairly quickly (I have a
very short runway for 2.0.x).

So who cares about this type of feature in 1.3.x? 
(I posted some code on 2/27 under subject "[1.3 PATCH] tracking the
active module", but that doesn't have to have any similarity with the
final solution)

So who cares about this type of feature in 2.0.x? 
(I posted some code today under subject "[PATCH] tracking active
request phase", but that doesn't have to have any similarity with the
final solution; I switch from original capability of showing the
request phase to showing the actual module name)

With regards to 2.1-dev, a few folks have spoken out on that already,
so I assume there is enough interest to make that happen prior to 2.2.
 I'm stuck on 2.0.x at the moment, and the requirement of preserving
binary compatibility may result in a significantly different
implementation.