The problem mentionned here is clearly reflected by the Zend\Mvc\View\Http\ViewManager class. When I see the numerous nested listeners that are registered on the bootstrap event, and also, the number of involved objects loaded potentially for nothing , I'm posing some questions about possible overhead and zf2 performances... Well the DI is not a rescue here but I did preferred see a delayed configuration/registration instead of a pre-configuration/pre-registration.. To resume, by reading the MVC code part of zf2 you will see that even without your own listeners you have a bunch of work that is done for each request and unfortunately, potentially (surely) for nothing.
Cheers -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/ZF2-Di-EventManager-tp4485022p4657188.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
