> I think the reasoning was that it wasnt configurable and there were > many conditions that would have prevented reaching the execution > filter so it was held off until it was actually required, no reason > carrying around baggage you may not need. I'm ok with it working > either way though, as long as the variables are more descriptive of > their contents.
Well, if Controller::forward() is called, you'll have ExecutionFilter::execute() called - after all, ExecutionFilter has the code that executes Actions and Views! You're definitely right about the variable naming, my fault ;) > I was thinking maybe it'd be better to not -require- the specification > of the execution filter and fall back on the old std, but that's not > consistent with everything else and if we do things like that here we > should do it everywhere and I'm not so sure I like the sound of that. > So if you wanna rename the variables to something else like you > suggested I'm ok with that. Yeah it would be a pain to do that everywhere. - David _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
