We've been examining the specifics of how to create event driven programs for the last several blog posts. But somehow, we need to integrate jQuery custom events with our server code. In this post, we'll see how we use Ajax to do just that.
In my last blog post, we took a more in-depth look at jQuery custom events to learn the specifics of how they're used. How, though, do you identify the events in your event-driven architecture? That's the subject of today's post.
I was talking with a friend recently about event-driven programming. He and I have been heavily into working with custom events for a few years. We've both seen the benefits of robustness and maintainability that event-driven programs provide. Why, I asked him, have more people not adopted EDP? His answer really surprised me.
Well, I finished that monster prototype, with much credit to my coding partner, Maciej. I figured that over 11 days, I worked 165 hours. Whew! Yesterday, we gave the presentation to a large multi-national corporation. To my relief and gratification, they were very impressed. Which leaves me, now, with only one small problem...
Yesterday, we looked at some simple server code that is called by events generated on the client. We saw that the server returns an EVENT property in its response -- but that my example never uses it. Today, we're going to see how that is used -- and why I think EDP is a BigDeal(tm).