Sun Java Plug-in - how to keep it loaded in IE at all times?

[Guest]

Does anyone know a way to keep the Java Plug-in loaded in the Internet
Explorer browser at all times, including across machine reboots, so that an
application launch in the day doesn't take as long?

Details:
The XYZ application is a third-party-vendor applet that gets downloaded to a
user's machine in one of two cases:

1) If no previous version of the applet has ever been downloaded to the
user's machine.
2) The version of the applet on the user's machine is older than the version
on the server.

We release new versions of XYZ applet very infrequently, perhaps 4 times a
year.

The issue we're experiencing is not with the applet caching, but with the
Java Plug-in load. Our users are complaining about the initial load of the
applet in the day. We've noticed that the first time the applet is launched
during the day, after a machine reboot or after a long period of inactivity
(a day or so apart from the last time the application was accessed), it takes
twice as long to launch the application. We've been researching this issue
and have discovered that the initial launch of the application takes twice as
long because the Sun Java Plug-in needs to get loaded. During subsequent
application access requests in the day, the application launches in half the
time.

 

[DanS]

Does anyone know a way to keep the Java Plug-in loaded in the Internet
Explorer browser at all times, including across machine reboots, so
that an application launch in the day doesn't take as long?

Details:
The XYZ application is a third-party-vendor applet that gets
downloaded to a user's machine in one of two cases:

1) If no previous version of the applet has ever been downloaded to
the user's machine.
2) The version of the applet on the user's machine is older than the
version on the server.

We release new versions of XYZ applet very infrequently, perhaps 4
times a year.

The issue we're experiencing is not with the applet caching, but with
the Java Plug-in load. Our users are complaining about the initial
load of the applet in the day. We've noticed that the first time the
applet is launched during the day, after a machine reboot or after a
long period of inactivity (a day or so apart from the last time the
application was accessed), it takes twice as long to launch the
application. We've been researching this issue and have discovered
that the initial launch of the application takes twice as long because
the Sun Java Plug-in needs to get loaded. During subsequent
application access requests in the day, the application launches in
half the time.

What is the time you are talking about ? How much, 5 seconds vs. 10
seconds ?

 

[Guest]

The Java 2 plug-in load takes approximately 13-18 seconds of the 25-30 second
delay the users are experiencing. Once the initial load of the plug-in
occurs, the
applet loads in about 10 seconds.

 

[Guest]

What is the time you are talking about ? How much, 5 seconds vs. 10
seconds ?

The SunJava plug-in load takes approximately 13-18 seconds of the 25-30
second delay the
users are experiencing. Once the initial load of the plug-in occurs, the
applet loads in about 10 seconds.