Geoffrey Young wrote: [...]
and in addition may be $r->current_handler, to return the current handler name? 'PerlOuputFilterHandler', 'PerlResponseHandler', etc.?
well, if we can do that then I don't see any reason to not stay with current_callback() - it's familiar, and I do kinda like the notion that the callback name is equivalent to whatever directive you (typically) use to set the handler (set/push_handler calls aside).
But then you won't be able to tell whether you are inside a response phase. The two are probably orthogonal. Since you can be in a phase A and handler B at the same time.
I did work on this a while ago but wasn't able to get it right - the async stuff with flushes made things flipflop between filter and content-handler rapidly. but it was a while ago - maybe looking at it again, having learned since then, will make it clearer now.
because that's exactly why it won't work. You are inside a response phase all the time, and you just go in and out various filter handlers. Or you could be in some earlier phases for incoming filters. I think it's be very handy to know whether you are inside a response handler or not, from inside the filter. (which is what you get now).
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
