Error handling, session expiration strategy in ajax asp.net application

Does anyone have a strategy or ideas for common error handling and session expiration in a large ajaxy app? In a traditional web application, when everything was published or received, it is easy to deal with errors and expiration of the session and present friendly messages to users. Not much with modern ajaxy web apps. My web application uses ASP.Net Ajax update panels and WCF calls from different pages. Any of these ajax calls may return an error or the user session may end. I am looking for one component on the client side or something that can recognize when there is an error and show the user a friendly message or find out when the session timed out and direct the user to the login page. What have people done to solve this problem?

+3
source share
1 answer

Session switching in general! This recommendation has 2 aspects.

  • AJAX is not such a fast technology, so server-side rendering time is improved in the Microsoft recommendation switching session.
  • A session in which 2 pages are open at the same time are considered, splits ajax into both of them.

You have already mentioned server-side failures, and the list of session minuses can be continued.

Instead, review your code for what you really need to save in the session. I am sure you can divide any data into 2 (magic number):

  • , (, ). cookie. ViewState , , .
  • , , . ( ). TempStorage, , - 3 , .
0

All Articles