Re: Downloading resource files for use by an applet
On Sep 8, 1:22 am, "John B. Matthews" <nos...@nospam.invalid> wrote:
Their "Java options" link mentions only applets, signed or unsigned.
Signed applets can do more than unsigned:
Java Web Start is the future:
...JWS is more flexible, but it
seems to have an all-or-none approach to security permissions at
Security for JWS apps. (applications or applets) can
be sandboxed, j2ee-application-client-permissions, or
all-permissions. The middle level would have to be
one of the more poorly named attributes. What is
a 'j2ee-app-client' when it is at home?
I have not used the middle level of permissions
much, it requires signed code, like all-perms,
but does not provide the same level of access.
Umm.. Here is a summary of some of the differences
in the permission levels available through webstart.
It is a table I prepared while developing the
JavaHelp webstart examples.
Just refreshing my memory from the table (no
wonder I do these things), the j2ee-app-client
permissions removes the window warning banner,
and allows prompted use of the web start services
to become direct use.
There are probably many other subtle differences
between the levels - I did not even try sockets,
for that example.
And while I am here, this table of download
constraints also comes closer to explaining
some things more directly relevant to the thread.
That same basic advice applies equally well to
applets and JWS launched apps.
Elsewhere in the thread I suggested using the
DownloadService, but note the webstart side of
the JavaHelp example is only considered from the
viewpoint of 'eagerly' downloaded files (when the
Jars are mentioned in the JNLP launch file), since
JavaHelp was not designed to work with lazy downloads.