AJAX Web Application Model
- AJAX Web application model resolve the major problem of synchronous request-response model of communication associated with classical Web application model, which keeps the user in waiting state and does not provide the best user experience.
- The AJAX application eliminates the start-stop-start-stop nature or the click, wait, and refresh criteria of the client-server interaction by introducing intermediary layer between the user and the Web server.
- The server response comprises data and not the presentation, which implies that the data required by the client is provided by the server as the response, and presentation is implemented on that data with the help of markup language from Ajax engine.
- AJAX Engine between the client and the application, irrespective of the server, does asynchronous communication. This prevents the user from waiting for the server to complete its processing.
- The AJAX Engine takes care of displaying the UI and the interaction with the server on the user’s behalf.
In traditional Web applications, the synchronous mode of communication existed between the client and the server as shown in following figure:
Since AJAX is essentially used for a partial update and asynchronous communication, the AJAX model used for programming and it is not restricted for use with specific data exchange format, specific programming language, or the specific communication mechanism.
- Responses to the user actions do not involve the trip back to the server as in the classical Web application model. Instead, the AJAX Engine handles on its own, such as data validation, some navigation and editing data in memory.
- The engine’s interaction with the server does not interrupt the user’s interaction with the application. In this way, the asynchronous communication is done with the help of the AJAX engine.