SPA single page application.

See this problem, the first to say their own understanding of the extent, and then refer to the amendment, to strive to understand this time to find out

Own understanding: Single-page application, to solve the embarrassment of the browser to get Data refresh page, through the AJAX request data to reach the asynchronous update view of the button, the principle of implementation by two kinds,

First, through the change of the hash value, the callback function of binding onhashchange updates the view, because the change of the hash value will not cause the page to lose its response and will not send the request to the server. The following is a list of several possible ways to change the hash value, changing the hash in the URL. The browser fallback button may appear in the history of the URL contains a hash value is not the same, will trigger the event, as well as trigger with turtle Point of the link changes, and then through the JS directly get Location.hash to change the resulting event trigger.

Second, add records to the browser's history stack by using the same H5 Historyapi. The past method only achieves forward and backward and jumps by Back,forward,go three methods. To H5 more Pushstate,replacestate method. Pushstate is simply added and does not jump to that record, while replacestate, the length of the entire history of the replacement record does not change. Hitstory.pushstate (Data,title,url), writes the first parameter data to the URL and specifies the value of the title. A record is added to the history stack by executing a popstate event where popstate is used to listen to changes in history, which can be understood as listening to the browser back and forth. Executes Location.reload () after binding the Onpopstate event; History.js is used for patching because of compatibility issues.

SPA single page application.