276 CHAPTER 9 STATE NAVIGATION PATTERN Figure (Web server certificate)
276 CHAPTER 9 STATE NAVIGATION PATTERN Figure 9-11. Final solution used to uniquely identify the HTML windows, URL, and associated state In Figure 9-11, each browser window instance is unique and can be identified. For example, if the user requests /resource, the window identifier is A, and the state identifier is 11. If the user processes the data, /resource2 is retrieved with a new state identifier 12and window instance A. If the user were to copy the URL to a new browser instance, the URL /resource2#12 would be copied. The state identifier 12 would be loaded, but the window browser instance is B, and therefore the server knows a new window instance has been created, and a new history is being generated. The server will then associate the state 11with the newly created state identifier 13. Now both browser instances, Aand B, both share the state identifier 11 in their history. Then if the user clicks the Submit Query button of either window, Aor B, two unique results will occur that do not conflict with each other. If the example were a plane ticket application, two tickets that start at the same location but end in different locations could be purchased. A new state identifier is created when the page is refreshed. Considering that we can identify the browser instance by using the window name, the state identifier is not necessary. Using a window name as a state identifier creates a state that is accumulated and organized by resource. When a new browser instance and old URL are copied (for example, state identifier 13), the server is responsible for copying the old state into a new state. The downside of using an accumulated state is that it is not as fine-grained as a state identified by unique identifiers.
In case you need affordable webhost to host your website, our recommendation is ecommerce web host services.