Wednesday, February 08, 2006

How Ajax is Different

An Ajax application does not need the start-stop-start-stop nature of interaction on the Web by introducing an intermediary — an Ajax engine — between the user and the server.
Instead of loading a webpage, at the start of the session, the browser loads an Ajax engine — written in JavaScript. This engine is responsible for both rendering the interface the user sees and communicating with the server on the user’s behalf. The AJAX engine does not allow user to stay idle . It makes user’s interaction with the application to happen asynchronously — independent of communication with the server. So now user don’t need to watch an hour glass after they clik on any link.

Following image shows the work of AJAX:

AJAX engine is cable of handling some simple task of it’s own like simple data validation, editing data in memory, and even some navigation. So for such simple task no communication to server is required. Now each user interaction which would normally take the form of HTTP request is now takes the form of a JavaScript call to the Ajax engine instead. If the engine needs something from the server in order to respond — if it’s submitting data for processing, loading additional interface code, or retrieving new data — the engine makes those requests asynchronously, usually using XML, without stalling a user’s interaction with the application.

That's all from today. Please let me know whether you liked this post.

This page is powered by Blogger. Isn't yours?