Comments on: Event-Driven Web Application Design

By: Juho Risku

Juho Risku — Tue, 23 Jan 2007 16:56:40 +0000

Just a note, our Helmi Open Source RIA Framework has a fully implemented event driven application programming model for AJAX / Rich Internet Applications, including passing the events to server and very efficient AJAX communications components. Excactly a kind of platform as described to be ideal in the article. So, download our User Interface Framework and start developing event driven web applications today. :-) http://public.helmitechnologies.com

By: Silly

Silly — Mon, 22 Jan 2007 02:10:59 +0000

Jacob, while you talk about it, others have been doing it for a long time.

Google “Echo2″

By: Jason Carreira

Jason Carreira — Fri, 19 Jan 2007 18:01:24 +0000

I agree with doing event-driven design… This is exactly why I implemented topics for publish / subscribe programming in Dojo. It was pretty trivial thanks to the great AOP stuff in Dojo, but I’ve got to stake my claim to something ;)

By: Wojciech Siudzinski

Wojciech Siudzinski — Fri, 19 Jan 2007 09:13:17 +0000

I think this is good aproach (i’m using YUI and CustomEvent) and maybe a way to create flexible apps. I agree with Chris that we still don’t realy know how to build web apps. We need solid guidelines. Event-Driven web app desing can be one of them.

By: Chris Heilmann

Chris Heilmann — Fri, 19 Jan 2007 01:35:49 +0000

I am amazed that every time there is a post about “you guys are not real” the poster doesn’t add a real name. :)

By: grinktt3n

grinktt3n — Thu, 18 Jan 2007 20:01:59 +0000

Sounds like we’re moving towards reimplementing X-windows cross platform. :)

By: Matt

Matt — Thu, 18 Jan 2007 20:00:59 +0000

Second abc’s comment. Dion, part of why I come here is for critical commentary! Thanks :)

By: abc123

abc123 — Thu, 18 Jan 2007 18:41:59 +0000

Are you getting paid for your awesome “Do you agree?” addition to his article?

this place rocks lol

By: Jacob

Jacob — Thu, 18 Jan 2007 18:18:43 +0000

we talked about something similar at JavaOne last year about taking Dojo or YUI widgets on the client and pairing them with Server-Side components such that events, with a proper ID scheme could be routed back up and executed on the server, leaving a 1:1 relationship between what would be service end points and client-side widgets. The benefit here is that the end developer just says they want a ‘datePicker’ component and the Server-Side framework will mediate the events and end points for you– leaving you with a single widget declaration, not a single widget declaration, then coding/publishing N endpoints to supplement the one widget.

By: Scott Schiller

Scott Schiller — Thu, 18 Jan 2007 17:20:03 +0000

Wholeheartedly agreed. In the ideal case, a developer should be able to attach hundreds of handlers to individual objects for separate events (eg. mousedown, click and so on.) My experience has been that in reality, browsers really choke with dynamic assignment and removal of large numbers of event handlers, so the delegation model (ie. a top-level listener which routes events as necessary to targets of those events) works excellently.