|
Quick Lists
|
|
Bug ID:
|
6764455
|
|
Votes
|
0
|
|
Synopsis
|
Avoid network requests if everything is cached and JNLP has <update check="background">
|
|
Category
|
javawebstart:general
|
|
Reported Against
|
|
|
Release Fixed
|
6u14(b03)
|
|
State
|
11-Closed,
Unverified,
request for enhancement
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
6763369
,
6838214
|
|
Submit Date
|
28-OCT-2008
|
|
Description
|
In the ideal situation webstart startup logic should behave as follows:
If all of the following is true:
a) initial JNLP file is local (even if it is in browser cache yet)
b) all required JNLP files contain <update check="background">
c) all required resources are present in the cache
Then startup of webstart application should not require any network requests.
Background thread should check for updates and install updates to the cache.
Posted Date : 2008-10-28 09:27:36.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Reuse background update logic introduced for plugin2.
Attempt to start from cache only. If this fails then try again with network connections enabled. In case if application fails with error mark it as one requiring foreground update check (to check if update will resolve the failure).
Posted Date : 2009-02-25 23:44:33.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |