> > I spent hours arguing with a friend who does exclusively > > .NET stuff about event driven web apps. As long as you > > have to reload the entire page, procedural seems like a > > much more logical way to go. You start at the top of the > > page, and go until you get to the end of the page, and then > > stop. > > But that isn't the only option - Flash widgets (or even full > Flash apps) mean that a single rendered page can make multiple > requests to the server before the page needs to be reloaded. > That's an important step forward and a reason why event-driven > applications are important. Flash allows genuinely asynchronous > events, breaking down the procedural model.
Yes, but those events need not be mapped to server-side "events". Since there's no way, currently, to map these client-side events automatically to server-side code execution, what's the value of a server-side event model in this case? Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
