My focus for the upcoming Lyons release has been on Dream plumbing for sending messages between services in the form of the chainable PubSubService. Largely this bit of infrastructure is going to invisible to the average user, but over the next couple of cycles, I hope that it will form the backbone for more decoupled processing in Deki.

With Lyons we will be exposing a lot of events that happen in deki for subscription via the basic pubsub backbone. This means that instead of having to dig into bowels of Deki, to find out when a page changes or a user setting changes, etc. you can simply create a new, separate service that subscribes to the events you care about and have your code triggered on demand.

The (not yet complete, and still mutating) list of events exposed by Deki can currently be found here, although as we get closer to release it will move into the official Deki documentation.

But what does all this mean to you from an end user perspective? Well, the first visible feature based on this event system is the Page Alerts system (live on trunk.mindtouch.com ) that allows users to subscribe to page and page hierarchy changes and get email notifications of changes.