> When I think of "Event-Driven" programming patterns, it boils down to exactly > what you have described in your essay about why Loggers are no good (I loved > that one, and a real eye-opener of something one have taken for granted!).
Wasn't that Leo Sutic? > "Event-Driven" (call it publish/subscribe, notification or whatever) patterns > are introducing a very nice extension to the familiar call/return concept. > Unfortunately, the benefits are rather subtle, and not easily appreciated > until you scale up the complexity of a system. > And I think Alex has noticed that, and seen that the next level is the > 'router'/'hub', gives even more decoupling benefits. > > NOTE; There are some traps in "Event-Driven" patterns, where the Events has > the 'trend' of moving from the low-level towards the higher levels, and the > "Call/Return"s are made in the opposite direction in the object hierarchy, > causing some really serious trouble in multi-threaded environments. People > interested; Join my Advanced Course ;o) I'm not touching that with a ten foot pole - I've already gone over my daily time allocation for dealing with emails :-). Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
