Hi Matthew,
I'm concerned that this code is being pushed into ZF1 so soon. In my mind (tonight), PHP event driven programming boils down to how processes are either registered or implemented. And with the right SOA this isn't really a problem. Furthermore, registering event listeners/handlers in PHP from a performance point of of view could happen in various ways (some may still be unknown to me). Yet in another thread you stated that in the next ZF2 beta release you would like to iron out if and how event listeners can be retrieved from the DIC. This concerns me in that we may now end up going down a 'bolted on' path within ZF1 (and ZF2). As you know, I am extremely concerned by the usage of the StaticEventManager. I would also say, that as you previously stated that this concept was modeled after a Java implementation, that I am concerned about its usage in PHP. Back then when I read the Java documentation (which I can't find anymore), it was not very elaborate, but given that static usage in a Java web application is significantly different than within PHP as that static Java resources persist across all web requests, it leads me to believe that the static usage in Java is only for low level processes, e.g cache, profiling etc - although it was not very explicitly stated as such in their documentation. However, to date in ZF2 the usage of the StaticEventManager is for high level processes that cannot be contained, as you say, within the object the graph. I would like to see event handlers, but I would rather wait to see it solidified in ZF2, with well defined use cases, prior to it being back ported to ZF1. This suggests to me, that we would need to see a ZF1 DIC implementation first. Regards, Greg -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
