Can you please explain your use case? Why would you need another `.pre` event? We already assured that it's a bad idea to have `.pre` and `.post` events when we have priorities and can throw logic at a stack of listeners instead...
Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 24 January 2014 13:20, dolphin <[email protected]> wrote: > Yes, thank you , I know these events . But I meant something else. > At these events, another "target" - Application. > As I've said , "dispatch" in reality works as "dispatch.post". > So I have to create a "capture" method for the event MvcEvent :: > EVENT_ROUTE. > This method uses RouteMatch and ControllerManager to pre-load the main > controller . > So I can emulate event "dispatch.pre". > That is, my code does the same job as the framework. As a result - wet > code, > tangled code , low productivity . > It looks just awful. Events are designed to avoid this . > This is the reason for my interest. > > > > -- > View this message in context: > http://zend-framework-community.634137.n4.nabble.com/ZF2-dispatch-pre-tp4661523p4661525.html > Sent from the Zend Framework mailing list archive at Nabble.com. > > -- > List: [email protected] > Info: http://framework.zend.com/archives > Unsubscribe: [email protected] > > >
