Event Driven Programming?
One of the things we'll be working with in the class next week is event driven programming. Instead of the front controller pattern used by the popular ColdFusion application frameworks (Fusebox, Mach-II, Model Glue), I'm using a decentralized approach that lets both clients and servers (through a proxy) listen for events and respond.
I find this approach has benefits and drawbacks. The drawbacks are inherent in the approach: it's decentralized. Unlike, for example, Fusebox -- where all the fuseactions are viewable from a single file -- this approach scatters actions throughout the code.
The benefits, though, are considerable. Adding functionality into a site is much, much simpler. Maintenance is easier. Testing is easier. And because a good deal of the work is done on the client, applications are much more responsive and have more of a desktop feel.
How about you? Anyone experimented with event driven programming and have any experiences/comments to share?
(If you're interested in learning how to do event driven programming, I'll be holding a class on UX progrmming for ColdFusion developers Apr. 20-24 in Las Vegas. We should have more info and a signup available soon.)


http://edmund.riaforge.org
Delete is an extreme example, but any system of passing events between pages seems especially susceptible to random events and possible out-of-order execution.
Any thoughts?
http://tv.adobe.com/#vi+f15384v1007