Caching options set in Presentation Manager do not affect the browser's temporary cache (which is controlled by the browser's configuration settings), but rather determine whether certain files are installed on the client.
Caching options handle Java files associated with Presentation Designer applications and Terminal Viewers Java configurations when a presentation that contains either of these items is selected on the myAccess Links page.
When the Java files are cached in this way, a user does not have to wait for the files to download the next time he or she accesses the presentation. However, if the Java files are updated on the server, the user might not receive the latest version. (This applies only to the Java code itself; configuration changes are always downloaded.) To receive an updated version, the cached files must be removed manually.
The caching options set using Presentation Manager take precedence over any caching options specified by the user on the Cache Preferences page. For example, if the Caching option in Presentation Manager is enabled, and the user selects No on the Cache Preferences page, the Java files are still cached. The caching options specified by the user on the Cache Preferences page take effect only when the Caching option in Presentation Manager is set to Ask User.
|Netscape Communicator 6.0 does not support caching Java configuration files at the client. Only application files can be cached.|
|To set the default Caching option|
The Presentation Manager tree appears.
The Manage myAccess Links page appears in the Management panel.
|Removing Cached Files at the Client|