Your administrator may have chosen to use the Cached Client option. What it does is store a copy of your start-up file on your PC and speeds the connection process (no download from a Web page is needed). It will also automatically update itself when it senses that your administrator has updated it. No information from your PC is sent to the server.
ResQNet provides a cached version of its client that is installed into a user's browser and remains there, resident, waiting for a ResQNet session to begin.
The cached client is used to cut download times. While users on a corporate intranet rarely notice the delay--between connecting to a ResQNet start up HTML, the download, and the beginning of a session—dial-up clients, especially those with older modems, will notice the time it takes to download ResQNet.
The Cached Client provides a way for administrators to automatically install and update a copy of ResQNet's Java classes. In effect, client's will only need to sit through a download the very first time they connect to a session or when changes have been made to their profile.
Cached client works in the following manner (after the initial download: approx. 1.5 MB): When a user connects to the ResQNet start up HTML a small Java program is downloaded and activated that looks at the cached client on the user's machine. If the version is identical to the version stored on the server, ResQNet is started locally from the user's machine. If, however, the versions are not identical, the user is asked whether they would like to download the updated cached client (the user is also asked when the cached client is first installed).
If the user ever refuses, the current ResQNet client is downloaded but not installed. Users will have access to a host session, but will have to sit through a download the next time they connect to a new session.
Manually Removing the Cached Client Files