Without the need for an applet launcher or JNLP extension,
or setting up the native library folder for applications,
we automatic cache the JAR file,
verify it's certificate (for non applications) and load the content.
.. this simplifies the tag and need to write a JNLP file.
The native JAR download mechanism still benefits from the applet's
network cache mechanism, hence downloads the JAR only
- if it doesn't exist, or
- if the server version is updated
Of course, this causes a network connection but surely not a big deal
and more correct. Users can still use the JNLP mechanism of course
using the JNLP tag:
<update check="background" policy="always"/>
Applications don't need to worry about the system dependent way
of dropping and publish the native lib folder anymore.
Applications also load the native JAR file and use their native libs,
just deploy all JARs in the same folder - done.