|
Quick Lists
|
|
Bug ID:
|
4784292
|
|
Votes
|
0
|
|
Synopsis
|
java web start should use cached jnlp file if possible to improve startup time
|
|
Category
|
javawebstart:general
|
|
Reported Against
|
mantis-beta
|
|
Release Fixed
|
1.4.2(mantis-b11)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
|
|
Submit Date
|
25-NOV-2002
|
|
Description
|
when we launch java web start with:
javaws http://your_jnlp.jnlp
Java Web Start will go out to the url to get the jnlp file, even if there is cached copy.
We should use the cached copy to launch if possible to improve start up time. (our update check later in the launching process will pick up the updated jnlp file if there is any)
|
|
Work Around
|
N/A
|
|
Evaluation
|
should fix in mantis to improve startup time
xxxxx@xxxxx 2002-11-25
|
|
Comments
|
Submitted On 23-NOV-2004
jgarza
It actually takes the cached copy for me, but ALWAYS. That is, it takes local jnlp even if the one in the server has changed.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
