For 2.0, I am thinking to remove action filters in favor of behaviors. As you know, behaviors can respond to events of their owners. Using this mechanism, it is possible to make a behavior to work like a filter.
Of course, there are still some differences between filters and behaviors. Below are the ones that are not easy or straightforward enough to implement filters using behaviors:
Filters’ before and after methods are properly nested.
If an inner filter’s before method quits, the outer filters’ after methods still get chance to be executed.
Could you please explain or provide more details about what are the intended benefits of removing the feature? Think that it would help ppl giving feedback. (like improve performance, simplify app flow…)
Concept behind behavior is very difficult. Why do you need remove simple filters (or so called "events" that rise on certain controller event)? With filters I can do simple and usefull thing: create some filter (filter-class), use some model in this filter and do usefull functionality making use of this model. I can do usefull functionality in needed places:before action execution, after action execution and so on. For example it can be redirection to another page if it is used before action. So it is obvious and I can use one model and one filter-class for all controllers in my project (because I can set one filter for all controllers in the same time via one or two lines of my php code).
When I read documentation I don’t understand that filters are the same behaviors. I think filters are closed to events. So I am confused when read this post. IMHO: I think if you remove “filters” you make some useless stuff or something bad.