Matthew Setter has a new post to his site for those wanting to take their first steps into Zend Framework 2. In it, he gives a gentle introduction to the Event Manager part of the framework - what its role is and how to customize it to your needs.

Enjoying the introduction to Zend Framework 2? I hope so. In part one of the series, we looked at Dependency Injection, otherwise know as the Inversion of Control principle. Then, in part two, we looked at Modules and the ModuleManager, the next key aspects. In this part, we started to work through what they are and stepped through how to build one from scratch; along with some pointers for taking them further. In this, the 3rd of 4 parts, I’m taking you through the next key aspect of the framework – the EventManager.

He starts with a graphic showing its overall functionality - an implementation of the Observer design pattern - and a general description of its goal (basically, execute code when actions are triggered). He talks about its implementation of aspect oriented programming and its event-driven architecture. Then he gets into some code-based examples: checking a query parameter on a dispatched request and logging form data before and after validation.