JDK-4402826 : Quicker update download
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_nt,windows_2000
  • CPU: x86
  • Submitted: 2001-01-08
  • Updated: 2001-03-15
  • Resolved: 2001-03-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.0.1 1.0.1Fixed
Related Reports
Duplicate :  
JDK-4425761 - Update notification dialog can be hidden and cause app. to look frozen
Description

The 1.0 release detects an updated to an already cached application
in one launch, and then do the actually download in the second
launch. It displays a dialog informing the user about this.

This behavior seems to be widely confusing for both customers and
developers since they want to use an updated version right away.

A new scheme should be designed and implemeted to improve the
perveived behavior. (see suggested fix)
rene.schmidt@eng 2001-01-08
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.0.1 FIXED IN: 1.0.1 INTEGRATED IN: 1.0.1 VERIFIED IN: 1.0.1
31-08-2004
PUBLIC COMMENTS When javaws 1.0 launches an application from it's cache, it begins a background thread to see if an update is available. If one is, it puts up a dialog saying that an update is available and will be downloaded next time. People would rather download and run the newer version at that time.
31-08-2004
EVALUATION The update check has been modified as per the suggested fix, with the following changes: 1.) The update chack will only timeout if <offline-allowed/> is specified in the jnlp file. For applications that don't allow running offline, the complete check for update will allways proceed launching. 2.) The default timeout amount is taken from the config file javaws.cfg at javaws.cfg.updateTimeout, the default default is 1.5 seconds. andy.herrick@East 2001-02-14
14-02-2001
SUGGESTED FIX The update detection/download scheme could be changed to do the following: - Spawn thread to do update check in the background - Wait w/ timeout (say max 2 secs) for result - continue launch with the above information. The update check will basically do the same as for 1.0, except that it does not show a dialog, but instead does a notify of a potential waiter. - Do update check - Set status - Notify all potential waiters rene.schmidt@eng 2001-01-08
08-01-2001