You should think of an AJAX web page as of a classical client-server application. The client is implemented with JavaScript classes, running within the browser's DOM. The server is your ASP.NET AJAX-enabled web form. The client and the server communicate asynchronously and once initialized, the client runs independently from the server, and is operational even if the server is unavailable.
In an AJAX application the communication with the server can be broken in several ways:
-
Longer period inactivity at client side can cause disposed session at the server (the complete server side state of the application is lost).
-
The ASP.NET web application is restarted at the web server because of modified web.config, global.asax etc.
- The web server is lagged or unavailable (no response is received within a reasonable time).
-
The Internet connection is broken (the server IP cannot be resolved and an instant error is returned).
During the time in which the server is not responding, a reasonable and customizable message is displayed by Nevron web controls. When the communication with the server is available again, the web control automatically resumes its normal operation. If the server session has expired or the web application has been restarted, the server side state of the web control is recreated and the user can continue using the AJAX capabilities of the control in his web browser.