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.
                                     

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


                                     

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
                                     

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