The mail component contains HTML, JavaScript, and JSP files. These files have .html, .js, and .jsp extensions. These files are transmitted to the browser and used to retrieve dynamic contents from the server using a proprietary HTTP protocol. The mail server provides user interfaces for the integrated mail component of Communication Express. The JavaScript files are shared by both these interfaces, and in general provide functionality for the application.
The CSS files that are used in mail are:
mail_css_ie5win.css
mail_css_ns6up.css
master-style.css
master-style_ie5up.css
master-style_ns4sol.css
master-style_ns4win.css
master-style_ns6up.css
Table 4–1 Displays the Different JavaScript Files That are Used in Mail.
Table 4–1 JavaScript Files that are Used in Mail
JavaScript file Name |
Application |
---|---|
Detects the browser to select which .css file should be used |
|
Maintains the common user interface codes shared by messaging listing and Search message result listing |
|
Checks for Domain security |
|
Maintains the initialization and globally shared functions |
|
Utility functions |
|
dtree.js |
User interface codes for folder tree |
The frame work related file is en/mail.html, which is the first file loaded by the browser.
The Mail page is configured to display the Mail page. It creates a number of frames, including several invisible frames. These invisible frames are used to pull the dynamic contents as JavaScript objects from the server. Once downloaded, the hidden frame can invoke the specific callback function in frameset HTML (_lr_fs.html) to render the updated dynamic contents.
Mail can be perceived as a dynamic client-side HTML engine. There are not many standard HTML statements in _lr_fs.html files. It is the ListFrameHTML() function in _lr_fs.html files which is responsible for the HTML output. This action takes place when ListFrameHTML() accesses the JavaScript objects from the hidden frames such as cfgFrame, msgFrame, and mboxFrame to generate the dynamic HTML page.