Routed events Address a Problem

Most applications are event-driven, and the POCO event system works pretty well. But compare it to this real-world situation:

In a traditional kitchen, the sous chef (pronounced “sue chef”) checks orders before they are assigned to line chefs to be prepared, and then checks the orders before they are served to customers.

If we were modelling this process, both the OrderPlaced, and ItemPrepared events would be sent first to the SousChef class, which would have to raise additional events for the next step in the process.

Every LineChef would have to register a handler for the ItemAssigned event, and the SousChef class would have to register a handler for the ItemPrepared event of every LineChef (which means the SousChef would have to know about every instance of LineChef, which raises issues of its own).