Geoffrey Young wrote: [...]
I don't think that's how it'll work. I was thinking of having a subroutine with a special attribute. So after the module has been compiled we can walk through all the CODE entries and check whether any of them is having the FilterInitHandler attribute and take it from there. Does this sound good?
you mean something like sub my_update_mtime : filter_init {}; ?
Yes.
I guess that's ok. it really depends on how the other interfaces work. I like the streaming filter API, and wouldn't want to deviate too far from that model to get this to work. and $filter->init (or whatever) is a bit more like the other calls.But the $filter object doesn't exist till it was called by Apache, it's created dynamically when Apache calls the filter. So I'm not sure where you want to call $filter->init(). If this can be done in the first filter invocation, like I've suggested in my first reply using the ctx flag, than you have this feature already. Please try it and let us know if it does what you want.
__________________________________________________________________
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
