Webstart Chrome after 100th download

Question

We have a Java application that our clients run through webstart. We have some usability issues:

Up to hundreds of clicks on the link for the jnlp file, chrome simply downloads the jnlp file, it indexes it by index: index (1) .jnlp, index (2) .jsp, etc. and launches the application. But after 100 downloads, when the user clicks on the link, chrome opens the "Save As" dialog. Then the user clicks on save; and chrome asks: "This file already exists, do you really want to replace it?" And the user says yes, and chrome loads jnlp, etc.

This process creates usability issues. To avoid this, we regularly changed the jnlp file name. But when users first click on the new jnlp link, chrome asks: "This type of file can harm your computer. Do you want to save ....... jnlp anyway?" before downloading the file. And this creates another step when you click another button. And of course, this scares the user.

Despite the chromatic handling of the problem, Firefox smoothly continues to increase the number of file names after 100.

How can we solve this problem with chrome without asking the user about some complicated settings on our computers?

Answer 1

Ask JNLP to set the desktop shortcut and menu items. Thus, they only need to “download JNLP” once!

The two icons on the right ( JotPad and Star Zoom Animation) are Java-based applications installed using Java Web Start. Since JotPad is tagged in the sandbox, the user will be prompted to create a shortcut. This selection is not offered for applications. with a higher level of permissions, so it would be wiser to set / remove shortcuts and menu items with the help of IntegrationService - which allows the application to be used (after asking the user) to create / delete them at run time.

Answer 2

Easy. Just tell them to change their boot options so that he asks where to save them each time, and then tell them to remember the path name. The next time they want to run the application, they can simply open the already loaded JNLP, rather than loading it again. Or tell them to use a browser, such as Internet Explorer or Opera, that downloads to a temporary folder rather than saving the file every time.

Answer 3

I solved my problem as follows: Once a month I rename the JNLP file and, of course, modify the html file containing the JNLP link. Within 30 days, it is unlikely that the user clicks and downloads the JNLP link more than 100 times.