-----Original Message-----
"jerome" (
[email protected]) said in
Java Web Start, although I don't use it (have it disabled so it does NOT
load unless I manually start it), is an application cache. When you run
Java applets, then get downloaded. Everytime you revisit that web page,
the Java applet gets downloaded again. If you use that applet a lot,
you end up wasting the time to re-download the same applet over and
over. Java Web Start caches Java applications (but does check if the
applet has changed). I think this requires connection to a web site
that is running the other half (i.e., the Java Web Start server) in
order to check for newer versions of the Java application. This is the
situation where the user pulls the Java application from the web site.
I believe you can also push the Java applications to ensure users are
running the latest version of your Java application. This is probably
the real advantage of using it. You can also ensure users have the
minimum version of the JRE (Java Runtime Environment) installed if
needed for your Java applications.
That's about as far as I did any research because I don't use it. To
know more, go read about it at
http://java.sun.com/products/javawebstart/index.jsp. Click on the
Documentation link.
--
_________________________________________________________ ___
*** Post replies to newsgroup. Share with others.
*** Email: domain = ".com" and append "=news=" to Subject.
___
.
