Over the years, dynamic capabilities were added to web pages, allowing a page to update itself and perform sophisticated data processing. Even so, the usual practice was, and in many cases still is, to send the server a request to update a certain item of information on the page, in response to which the server sends an update of the entire page.
Ajax uses client-side JavaScript together with XMLHttpRequest in order to receive data from the server without refreshing the entire page. Saving the need to reload and the ability to get only the necessary information from the server improve response time and performance, and make it possible to create a user experience that until now hardly existed in web applications.
When we talk about Ajax we are not talking about a specific piece of software or a single technology, but about a technique and an approach. The technique is based on several existing technologies and methods, whose use has become widespread and popular only recently.
In the Beginning There Was LiveScript
It all began when Netscape added to its browser a feature called LiveScript, which made it possible to embed short scripts in web pages, scripts that kept running even after the page had finished loading. LiveScript later became JavaScript and DHTML (Dynamic HTML). Later on, XML gained momentum and it became possible to update an HTML page according to XML data.
The term Ajax was coined by Jesse James Garrett of Adaptive Path, in an article he wrote on the subject, as an abbreviation of Asynchronous JavaScript+CSS+DOM+XMLHttpRequest. Today Ajax is gaining popularity (an Evans Data survey shows an annual increase of 11% in its use) and is an important trend in web development, like familiar technologies such as Java, ASP or C#. It can be said that the whole Ajax concept now fits into the broader concept of the next generation of the Internet, known as Web 2.0.
The spread of XML led Microsoft and Mozilla to add to their browsers a function called XMLHttpRequest, which allowed JavaScript code to fetch additional information from the server using XML. The new function was added shortly before the bubble burst, so development in the field stalled somewhat - almost no one made use of XMLHttpRequest.
It seems the first to grasp the potential of using XMLHttpRequest together with JavaScript were the resourceful entrepreneurs at Google, who built on this technology the first prominent applications, such as Gmail, Google Suggest and Google Maps. These applications gave the entire field a push forward and wide exposure. Further examples of the use of Ajax can be found on leading sites such as FeedFeeds, Internet Bargain Center and Couloir.
ECMA Script
The scripting languages that can be used with Ajax are ECMA-compliant scripting languages. Many people refer to ECMA Script as JavaScript, but this is not accurate. In 1995, Sun and Netscape developed JavaScript, support for which was first included in Netscape Navigator 2. In light of its success, Microsoft developed a similar language called JScript, which was first supported in Internet Explorer 3. In response, Netscape asked to standardize JavaScript at the ECMA International organization. ECMA issued, based on JavaScript, a specification called ECMA-262, also known as ECMA Script.
An Ajax implementation brings a website closer to what is called RIA (or Rich Internet Applications) - web applications that deliver a high-quality, rich user experience, much like a regular application. From the organization's standpoint, this is a significant improvement for online services, but on the other hand it also has numerous drawbacks, such as browsers that disable the use of Ajax, and no support for browsing backward.
Implications for Users and the Organization
Using Ajax on an organization's websites and intranet will benefit users first of all. They will enjoy a high-quality user experience and friendly, fast, sophisticated and efficient applications. Ajax will reduce the load on the organization's web servers and provide improved resilience to communication outages. For the organization, this is mainly about creating something advanced, innovative and modern.
Frameworks
Today there are numerous tools for developing Ajax applications. Among them are frameworks, a kind of library that does part of the work in place of the programmer, which simplifies working with Ajax. Here are some of the most common ones: Ajax .NET Professional, Magic Ajax, Ajax Anywhere, Ajax Tags, XAjax Library, AJASON and Plex Toolkit.
According to Forrester, Ajax does not meet all web development needs, but it suits 80%-90% of what most organizations require. In addition, they are suitable as clients for the user, for communicating with web services.
Summary
This is "the next big thing" in website and web application development. If you are building a new site or upgrading one, it is worth getting to know this useful technique.
The summary is taken from a pCon investigation titled Ajax - Browsing Fast.
Extensions, expert interviews, practical tips and links for further reading can be found at -
http://www.pcon.co.il/v5/Debrief.asp?debrief=772