AJAX-Design Patterns

As we all know, the so-called "no-refresh application" based on AJAX generally refers to the use of XmlHttp components in WEB applications to achieve certain non-refresh page switching based on JavaScript background asynchronous data transmission to replace the traditional "refresh-free" application based on HTML links. Refresh" page switch.

This kind of non-refresh effect is really cool, but after trying it for some time, thinking developers will find the biggest problem: since I have no refresh, then for a set of non-refresh functions, that is, from opening Starting from the web page, all effects are asynchronously calling XmlHttp through JavaScript in the background of the current page to transfer data and replace the display content in the current page. There is no traditional "with refresh" page switching. However, if in a certain state, the page pauses loading due to network problems and needs to be refreshed manually, or the user wants to manually refresh the current page to obtain updated data, or even accidentally presses "F5" or the What happens to the Refresh button? By the way, this is the worry raised by the title of this article. If there is no special processing, then after manually refreshing the page, the content on the web page will naturally return to the originally displayed content, instead of the data we really want before manually refreshing. Did you suddenly feel depressed again? :) No need~~