Active Client Pages: Completing the Code for a Browser Example
The aim of this five-part series is to show to what extent a major browser responds to ACP. ACP is a new technology. In order to understand how a browser responds, we need an example to use to test the browser. We need to understand the example first. In this third part of the series I complete the explanation of the example.
Active Client Pages: Completing the Code for a Browser Example - The window on the right at Level 3 (Page 4 of 4 )
This window has not been indicated in fig 3.1. However it exists. It is the window that contains the Doc1 and Doc2 documents. When you create the window, you create Doc1 automatically. Doc1 creates Doc2. In this section, we look at Doc0 and Doc1.
The window here is different from the other windows we have seen in the sense that it houses two documents. Each of the other windows in the session houses only one document, and no distinction has been made between the window and its document. Here there are two documents, and you will see some distinctions.
The content of Doc0 resides in the file, sendPge3Doc0Str.pl in the server. This is the file:
This is a Perl file, with two Perl statements as in the other cases. The content of the quote operator is an HTML page. This is the initial content of the window. Any window has at least one document. So this initial window content is a document.
The first statement in the function opens an output stream. The next statement writes content into the output stream. The third statement closes the output stream, and by so doing, creates a new document. Note that the method of creating a new document is different from the one of creating a new window.
It is time to take a break. In the next part of the series, we shall quickly look at the remaining code, and then we look at the features in the example that we shall use to assess the browsers.
DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.