The public who have come across GMail, Flickr, Google Suggest or Google Maps will become conscious that the latest diversity of lively web applications is growing. These applications seem and operate extremely similar to conventional desktop applications without relying on plug-ins or particular browser features. Web applications have conventionally been a set of HTML pages that must be reloaded and refreshed to achieve the transformation of any part of the content. Technologies such as JavaScript programming language and Cascading Style Sheets (CSS) have developed to the point where they can be used competently to build dynamic web applications that will run on most of the browsers.

Ajax is not a new prospect. These methods have been used by developers directing Internet Explorer on the Windows platform for several years. Until of late, the technology was known as web remoting or remote scripting. Web developers have also used a mixture of plug-ins, Java applets and hidden frames to pursue this interaction model for a while.

Using JavaScript technology, an HTML page can asynchronously make calls to the server from which it was loaded and acquire content that may be formatted as XML documents, HTML content, plain text or JavaScript Object Notation (JSON). The JavaScript technology may then make use of the content to renew or transform the Document Object Model (DOM) of the HTML page. The term Asynchronous JavaScript Technology and XML (Ajax) has emerged in recent times to clarify this interaction model.

What has altered recently is the addition of support for the XMLHttpRequest object in the JavaScript runtimes of the majority browsers. The magnificent thing is the consequence of the JavaScript technology’s XMLHttpRequest object. Even though this entity is not defined in the proper JavaScript technology specification, all of today’s mainstream browsers support it.

What makes Ajax-based clients only one of its kind is that the client contains page-specific control logic entrenched as JavaScript technology. The page interacts with the JavaScript technology based on actions such as the loading of a document, a mouse click, focus changes or even a timer. Ajax interactions permit for a comprehensible separation of presentation logic from the data. An HTML page can pull in bite-size pieces to be displayed. Ajax will necessitate diverse server-side structural design to support this interaction model. Conventionally, server-side web applications have focused their attention on producing HTML documents for each client event and it results in a call to the server every time. The clients would then refresh and re-render the whole HTML page for each response. Rich web applications focus on a client obtaining an HTML document that acts as a template or container into which the content is injected, based on client events. Using XML, data is retrieved from a server-side component.

The minor dissimilarities with the JavaScript technology and CSS support among present age group browsers such as Mozilla Firefox, Internet Explorer and Safari are controllable. JavaScript libraries such as Dojo, Prototype and the Yahoo User Interface Library have come out to stand in where the browsers are not as convenient and to make available an identical programming model. Dojo, for example, is dealing with user-friendliness, internationalization and superior graphics across browsers, all of which had been thorns in the side of former adopters of Ajax. More updates are certain to arise with the growing needs.

Tags: AJAX and Java Combination