pyrocms/pyrocms — pull request #1087 by obrignoni (2012-01-19 10:21:11+00:00)
Title: Feature/model triggers

The main idea here is to have triggers in most places where data changes so that other modules can react to more points in the core. All triggers pass the relevant data to the Events::Register(). For example, module rely more on PyroCache with caches that don't expire but are cleared when certain triggers indicate that data is changing. I already made a module that works this way. As i understand, one of the goals was to reduce queries in the frontend. Maybe this will help.

Maybe I went overboard with the number of triggers. I tried putting them in the best places. Let me know if you think some of them don't make sense.