If you look at this blog archive, you should see that I got interested in the MVC issue a couple of months ago. Generally speaking, I discovered that both me, and most of PHP programmers have actually never seen this architectural pattern, because web framework developers tend to call MVC something completely different. Yes, it originates from MVC, but the key concepts are different, and what is more – these derivatives do have their own names. I started wondering then, how a true MVC web application would look like, and what their pros and cons in the web environment are. Of course, I needed a playground to test these concepts and I came into an idea to create a sort of experimental framework that could help me to find the answer. This is how Trinity was born in late May 2010.
Symfony is not just a framework, but also a collection of extra additional libraries. They do not depend on Symfony itself, so they can be easily deployed in third party projects. They are quite well designed and tested, which gives us more reliable software, and the opportunity for better cooperation with other third party components. One of the libraries is Event Dispatcher focusing on so-called event-driven programming paradigm. In this post, we will see how to use it in our projects.