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.

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)
 xxxxx@xxxxx  2001-01-08

N/A

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.
 xxxxx@xxxxx  2001-02-14