Geoffrey Young wrote:
ok, but I don't understand why this can't follow the same mechanics of attributes, since they work just fine for the other stuff.
It's not the same. Currently we use attributes to learn whether the handler is designed for Request or Connection. But we already know the name of the handler. So we don't have to go through all $__PACKAGE__::{CODE} entries. With filter_init, we don't know how that function was named, and looking it up, might be slow.
ok, I guess I'm still missing something because I still don't get it. but it doesn't matter - I'm sure it will clear up in time :)
of course, you could show up on IRC someday and explain it to me :)
I'm there all the time, it's just that you are 19h behind me ;)
But then you create a whole new filter, so whatever work is done in filter_init is lost. I guess you could still pass notes via the connection record. I thought that you want to create a filter early, run init on it and then use the same filter to do the real filtering.[snip]
Nope, but first I want to add the add/remove functionality.
yeah, that was my thought. I started working on that but couldn't quite see all the pieces. here's what I have so far - it should compile cleanly and be good for a start, but it doesn't do anything (yet) due to the missing hooks.
__________________________________________________________________
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]
