S
Stefan Ram
When one follows a web link to an executable JAR on a
webserver, it will be transferred via HTTP and then executed
(for example, under Windows, after Java was installed). The
operating system might ask the user for a confirmation and
then will run the JAR.
Many users do not know much about what a JAR is, so they
might not be able to appreciate the possibly enhanced
security of Applets or of Web-Start (is there any?)
So, in order to enable someone to start a Java-Application
via the Web, what might be some reasons to prefer one of
those means above the other (a link to an executable JAR
versus Web-Start)?
webserver, it will be transferred via HTTP and then executed
(for example, under Windows, after Java was installed). The
operating system might ask the user for a confirmation and
then will run the JAR.
Many users do not know much about what a JAR is, so they
might not be able to appreciate the possibly enhanced
security of Applets or of Web-Start (is there any?)
So, in order to enable someone to start a Java-Application
via the Web, what might be some reasons to prefer one of
those means above the other (a link to an executable JAR
versus Web-Start)?