Let’s talk about AJAX. Not the detergent, although it does smell good. AJAX (in the Internet world) is a technology that allows a web browser to send and receive information to the web server without making the page you’re looking at refresh. That’s really all it is. I hear you saying “But what in the world does that mean?”

The idea is that if the page you’re viewing doesn’t refresh, and completely redraw itself a couple things can be accomplished:

1. Less information is transferred from the server. Browsers do a good job of caching things like images so that they don’t have to be downloaded again, but for every image on the page, the browser still has to ask the server if it has a newer copy. That’s a lot of talking back and forth, and it takes time.
2. The interface can be more responsive. If you’re viewing a long list of items, and you’re looking at the first page, when you click the next button your browser only has to load the next set of data — not all of the formatting, and images and what-not. Clicking on something doesn’t require everything to be reloaded again.
3. Money can be saved. (This is the part you business owners will like) Because less information is transferred overall, there will be lower bandwidth costs.

The concept behind AJAX has been around for a very long time. Swapping the processing of data from the server to the client and back again has been happening in cycles since the inception of the mainframe. AJAX in the form it is today has also been around quite some time. Around 1998 I built an application that used very similar ideas to get around having the page refresh, but in the past couple of years there has been a heavy focus by the web programming community to build code that does it in a very clean and efficient way.

As time passes AJAX will mature even further, and may become the core method in the way that browsers work, rather than simply one way of creating web sites.