The CakePHP core team is very exited to announce a major jump in the version numbering. CakePHP 2.0 stable is out! we have put endless hours into this release and great ideas have made it into the the framework for this version. [...] The overall CakePHP ecosystem has also been improved. [...] A huge thanks to all involved in terms of both contributions through commits, tickets, documentation edits, and otherwise contribute to the framework. Without you there would be no CakePHP.

Some huge changes have happened in this release including:

• Dropping PHP4 support
• Use of more native PHP functions
• PSR-0 compliance
• Object injection for libraries/components/helpers/etc
• Console tools completely rebuilt
• A move to PHPUnit tests (away from SimpleUnit)
• HTML support in form helpers
• Lazy-loading on just about everything making the overall experience faster
• Several new plugins like: DebugKit, Datasources, MongoDb, Migrations and AclExtras

They've created a few resources to help you get started with this new version including a new version of the book, a screencast and a migration guide.

Earlier this year, I wrote about Aspects, Intercepting Filters, Signal Slots, and Events, in order to compare these similar approaches to handling both asychronous programming as well as handling cross-cutting application concerns in a cohesive way. I took the research I did for that article, and applied it to what was then a "SignalSlot" implementation within Zend Framework 2, and refactored that work into a new "EventManager" component. This article is intended to get you up and running with it.

You'll need to already have an install of the Zend Framework (v2) installed to follow along. He covers some of the basic terminology and the base code the rest of the tutorial's built from - a simple EventManager instance with a trigger on it. He moves on from there showing how to specify targets for the triggers, setting up global static listeners and listener aggregates as well as how to short circuit listener execution. He wraps up the post by applying all of the examples into one simple caching tool that responds to the trigger by either sending back a new instance or pulling the previously generated one from the cache.