-- Greg <[email protected]> wrote (on Tuesday, 20 March 2012, 09:29 AM -0500): > On Tue, Mar 20, 2012 at 8:48 AM, Matthew Weier O'Phinney > <[email protected]> wrote: > > I've fielded a large number of requests > > from ZF1 users who would like the functionality for their ZF1 > > applications -- no more, no less. > > I appreciate that, but I'm still concerned that significant changes to > the Event system will cause disruptions to the ZF1 implementation. The > late pull request for the SharedEventManager could be one such > example.
These actually aren't terribly significant; it's primarily an implementation detail. The only difference we would need to make for ZF1 is that, because there's no DIC, we would likely use the static event manager by default. > Anyhow I realize its also about choice..... > > > > > > I actually haven't been discussing retrieving event listeners from the > > DIC at all -- I _have_ been discussing injecting a "SharedEventManager" > > into EventManager instances, so we don't need to use the singleton > > StaticEventManager version. > > Well this is the first ML post mentioning the SharedEventManager, and > my comment was based off a comment you made in another thread: > > http://zend-framework-community.634137.n4.nabble.com/ZF2-speed-td4414795i20.html#a4428769 > > I actually then stumbled on Symfony2's ContainerAwareEventDispatcher > which lazy loads listeners from the DIC. This is, again, however, an implementation detail, and would be code implemented likely in the MVC layer, not in either the DIC or EventManager. In other words, it's an orthoganal concern. <snip> > > Additionally, as explained before, there are no ties between DIC and the > > EventManager; the only question is if there's a way to alter the EM to > > be more DI friendly with regards to shared event collections. Since we > > have no DIC in ZF1 -- and no plans to backport it, as it relies much too > > heavily on PHP 5.3-specific features -- I see no conflict here. > > Thats another discussion I think, I don't want to come off overly > incorrect or harsh, so I'd rather wait to see how the ZF2 Definitions > evolve - but that doesn't mean it is impossible for ZF1 to have a > Container of some form. Again, as noted above, orthogonal concerns, and they're primarily directed at how applications are/will be written for ZF2, not ZF 1. We're not planning on backporting the DIC at this time; it's not scheduled for 1.12.0, which effectively means it's not happening for 1.X at this point. Rob brought up the proposed/scheduled components for 1.12 around a month ago for comment, and had no feedback along this line; at this point, code freeze is Friday. Again, this is a standalone component to give ZF1 users the ability to use an events system _in_ _their_ _own_ _code_ -- it's opt-in, and no ZF1 code is being refactored to use it. As you said, it's about offering a choice for end users. -- Matthew Weier O'Phinney Project Lead | [email protected] Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
