Kbase 18179: Apptivity FAQ How to cache CAB JAR files locally on client
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/08/1998 |
|
Apptivity FAQ How to cache CAB JAR files locally on client
When deploying Apptivity applets, it is possible to package the
Apptivity client classes and the applet classes in CAB or JAR
files for faster download to the client. For more information see
the deploy.html file in the redist directory under your Apptivity
installation directory.
The following FAQs may shed additional light on some of the
options there are for managing the time it takes for classes
to be downloaded from the server to the client.
Q. How can I prevent CAB files from being downloaded to the
client the second time an applet is run?
A. When you load an HTML page which contains a CAB tag,
IE will popup a window asking if you would like to install the
CAB file(s) locally. The first time the applet is run the user
must choose YES, and IE will download and install the
packages locally. The next time the user can simply choose
NO and skip the download and installation of the packages.
This will reduce the applet load time slightly.
Q. How can I prevent JAR files from being downloaded to
the client the second time an applet is run?
A: There is a Netscape Communicator flag that can be
set to use local CACHED files. To set the flag, do the following:
1. Go to Edit | Preference from Communicator's main menu.
2. Double-click "Advanced" from within the Preferences window.
3. Select "Cache" from the expanded list.
4. Clear cache if you wish and set caching values.
5. Also check the frequency of document comparison to 'Never'.
6. Click "OK" to enable the settings.
The following is a brief explanation of the flag settings and their
meanings:
To set the frequency that the document in the cache is compared
to the document on the network, select one of three radio buttons
to specify how Netscape checks the network for document
revisions (so that you're brought an updated page from a network
server rather than a potentially stale page stored in the cache).
Once Per Session (The default choice) - Checks for page revisions
only once during the time you start and quit Communicator .
Every Time: Checks for changes each time you request a Web
page rather than relying on data stored in cache. Since
Communicator is constantly checking the cached items against
the Web Page, you encounter some performance degradation.
Never: No verifications. You will receive no Updates. All pages
will be loaded from cache and the cache is never updated.
If the user knows that the JAR file on their local system is
up-to-date, they should set this flag to "Never".
UTF 8/12/98