And it Got a Name: Ajax

As I predicted, web-application developers are starting initiatives to move more of the web-application to the web browser. I talked about “some of the opportunities”: earlier, and also about moving much of the “UI logic to the browser”: Even earlier I mentioned that “it would be a good idea to develop a framework to make client-side browser work easier”: Recently this idea has been named: “Ajax”: — Asynchronous Javascript And XML.

But enough “I saw it all coming” patting on my own back: this is an interesting shift. Ajax is the new buzzword in the web-development world these days. People start to ask all kinds of questions: “is Ajax actually going to make the normal client-side non-web application useless?”:,1995,1777009,00.asp?kc=MWRSS02129TX1K0000535 “Is Ajax even a new idea?”:

For the unknowing, what’s this Ajax thing? I myself look at it this way: until now all the action in your web-application has taken place at the server-side. The user’s browser was only used for the view, to show the pretty charts, forms and reports. What’s the main problem with web-applications today? They’re unresponsive and don’t feel as rich as normal Windows (or Mac OS X, Linux etc.) applications. The solution? Move as much to the browser as possible. Only contact the server if it’s necessary. This not only makes your web-application more responsive, but also takes a lot of load from the server.

Does this actually work? Absolutely. Success stories are coming mainly from Google, which has become an expert on this technique, they include “Gmail”: and “Google Maps”:

If you search Google for “Ajax” right now, you’ll mainly find hits about the popular Dutch soccer club, but that will soon change.