Faster Java WebStart startup times?
Posted: Fri Apr 17, 2015 6:18 pm
Hi,
We've been experimenting with the Java WebStart deployment and everything works fine except startup times are prohibitively long.
This is caused by the fact that all the jars are downloaded eagerly every time, and then compared to the installed version (or re-installed) even if there has been no change since the last install.
Is it possible for the WebStart build process to create a build identifier file (maybe a simple, random guid) and that at startup only that file is downloaded eagerly, and checked against the copy of the locally installed version? Then of course if they're different the rest can be downloaded too and updated.
Thanks in advance,
Peter
We've been experimenting with the Java WebStart deployment and everything works fine except startup times are prohibitively long.
This is caused by the fact that all the jars are downloaded eagerly every time, and then compared to the installed version (or re-installed) even if there has been no change since the last install.
Is it possible for the WebStart build process to create a build identifier file (maybe a simple, random guid) and that at startup only that file is downloaded eagerly, and checked against the copy of the locally installed version? Then of course if they're different the rest can be downloaded too and updated.
Thanks in advance,
Peter