When using the Java Plugin with our application Jar
Indexing fails to work properly. In Java 1.3.1_02 &
1.3.1_03 on Windows this problem occurs. This problem was
not an issue in Java 1.3.0_02.

When our application makes a socket connection in the Java
Plugin, every time a resource is loaded from indexed Jar
files, those Jar files are reloaded over and over again
from the server. This causes performance to degrade to the
point that our application is almost not usable for our WAN
users. If the socket connection is not made then the Jar
file is only loaded once and each resource can be loaded
from that one Jar file without any reloading of the Jar
file from the server.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Compile Java Source as provided below.
2. Put class files in first Jar file.
3. Put resources (Images) in second Jar file.
4. Sign both Jar Files with a valid certificate.
5. Index Jar files using the jar -i command.
6. Put both files on a web server with HTML code to load
the applet in the Java Plugin.
7. Load the Java Plugin into the Browser by visiting a
generic applet.
8. Bring up the Java console and press 2 to display basic
and net debugging.
9. Run the Test applet.
10. Look at the console to see that the second Jar file is
being loaded over and over again for each image.