For anyone who wants to understand Ajax or how I am approaching it, start here.
Surprisingly the demand for such a "solution" didn’t really come about until 2005 when Ajax came on the scene. The real kicker seemed to be when Google started using it. Prior to this most end-users were quite comfortable with page-at-a-time forms submission and full page refreshes. If you ask most people, that’s just the way the net works. But when Ajax came around, all of a sudden people realized they had a problem that needed to be solved. This newfound problem and solution quickly became so much a part of the end-user consciousness (or at least business people charged with creating applications for end-users) that now most of my clients say they want it for new development. This is really funny because I’ve been asking people if they want something like this for years and never got a single request. Now I’m faced with the problem that most clients don’t want me to even start development on their projects unless Ajax-style functionality is present right from design. For those clients on the fence, I’m faced with the issue of starting a project without Ajax only to have them read up on it later and ask me why it’s not in there – then I’m faced with a re-write, but at whose expense?
As you’ll see as we go, AJAX is used often as an acronym, but the more savvy will refer to it simply as Ajax, calling it neither a technology nor an acroynym, but just a way of doing things.