Active Client Pages: Summary of the Document Phase of Chrys`s Approach
In this part of the series, I give you a summary of the Document Phase of my approach to Active Client Pages. In order to help you better understand this phase, I need to explain two other approaches to ACP. When I finish that, we will proceed to the next phase. It may seem a little complicated (this is, after all the eighth part of a 12-part series), but by the time we're done you'll understand a number of ways to make your pages load faster over a slow Internet connection, even when they're full of images.
Active Client Pages: Summary of the Document Phase of Chrys`s Approach - Summary of the Ajax Approach (Page 2 of 4 )
The Ajax Approach is based on Chuck Bradley’s work. The Ajax Approach does not use a Frameset. This is the summary of the Ajax Approach, including my enhancements.
The master page has a DIV element, which displays the pages.
While the user is working, data of any type, including program script code, is downloaded from the server in advance, without the knowledge of the user, by Ajax.
It is advisable to put the Ajax script at the bottom of the page. Each page can have Ajax script to download data in advance.
The downloaded data has to be stored in the JavaScript variables, JavaScript object properties and/or JavaScript arrays in the script in the HEAD element of the master page. The string form of a page that is downloaded should have only the HTML elements (sub strings) that would fit into a DIV element.
Pages are produced by script that is in the HEAD element of the master page or script in the BODY element of a page (content), downloaded.
There is only one document here, which is the master page. All the pages you see are HTML elements in a DIV element. These elements should not include the HTML, HEAD and BODY tags.
Summary of the Document Phase of Chrys’s Approach
This phase is my innovation.
The master page is the first page downloaded from the server by typing the address in the browser and clicking Go.
Other pages in the session are HTML documents developed and loaded at the client’s browser.
While the user is working, data of any type, including program script code, is downloaded from the server in advance, without the knowledge of the user, by external JavaScript tags or by Ajax.
It is advisable to put the Ajax script or external JavaScript tag at the bottom of the page, so that while the user is reading the page, the data will be downloaded. In this way the user should not perceive the downloading process.
The downloaded data has to be stored in the JavaScript variables, JavaScript object properties and JavaScript arrays in the script of the master page, which is the first document downloaded.
The Store is a moving store. As the next page is loaded, the store moves to it.
Pages are produced by script that is in the HEAD element of the master page or script in the BODY element of a page (content) downloaded.
The Back and Forward buttons of the browser are enabled with this approach.
This phase of Chrys’s Approach incorporates the Script and Ajax Approach to ACP.
Cookies as the store
If you can successfully use cookies as the store for the Document Phase of Chrys’s Approach, then please do so. With cookies you may not have to move the store as you load new pages. The problem with cookies is that their behavior is not yet standardized. I will write an article that gives you guidelines on how to use cookies with the document phase of Chrys’s Approach.
JavaScript 
How Browsers Respond to Active Client Pages
