maybe i'm totally naive, (ok probably more than maybe when it comes to any sort of programming, i tend to be better at xhtml/css/photoshop, and the occasional sound stuff etc). but if you are in need of user input/interaction, how would you not be tied in somewhat to the client side/GUI? ( which is probably way more of an issue on the web than desktop, where the gui is a little more consistent in the way that it responds and acts.)
That is really a client side issue, and not an server side issue. By the definition of event based architecture, I see this being solely server side. You can't depend, and nor should you, depend on the client, that's the number one rule of web development.
and what do you take/have as the definition of event based architechture? (seeing how i find there are 5 definitions for every programming word ever invented, quite annoying for communication purposes.)
do we have a thread that has a bunch of definitions of patterns/ vaque terms, and technobable (such as enterprise, dispatcher, w3c and etc?) somewhere here on sitepoint?