P4
A DESCRIPTION OF THE REQUEST :
Why JWS does not accept to modify the connection timeout, just for the duration of the connect attempt from JWS to the server ?
Adding, for example, <property name="sun.net.client.defaultConnectTimeout" value="3000"/> to the jnlp file (or -D in java-vm-args)
would change the System property just before the very short time when JWS tries to connect to the server (to know if there is a new dowload to do). JWS would then put the timeout back to the original value as soon as the connection has succeeded or timeouted.
This would not be very harmfull for the system, and much better for the user.
Another jnlp keyword could be created, like "connect_timeout" with the described action made behind the scene.
JUSTIFICATION :
If the server is down, the end user will be quite surprised to see nothing on the screen, will say that the application does not work, and that's all. He will not be confident and will not buy.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
When the server is down, JWS would detect this after a 3 sec (for example) timeout and would launch the application from the cache.
ACTUAL -
My application runs with offline-allowed and <update check="timeout" policy="always"/>
When the server is down, the application is launched after a very long time (2 mn ?), which is a disastrous end user experience.
CUSTOMER SUBMITTED WORKAROUND :
Supposing that a user reports the problem, tell him to modify the jvm args (with javaws control panel), by adding -Dsun.net.client.defaultConnectTimeout=3000.
If this works, it is not a commercial solution.
Why JWS does not accept to modify the connection timeout, just for the duration of the connect attempt from JWS to the server ?
Adding, for example, <property name="sun.net.client.defaultConnectTimeout" value="3000"/> to the jnlp file (or -D in java-vm-args)
would change the System property just before the very short time when JWS tries to connect to the server (to know if there is a new dowload to do). JWS would then put the timeout back to the original value as soon as the connection has succeeded or timeouted.
This would not be very harmfull for the system, and much better for the user.
Another jnlp keyword could be created, like "connect_timeout" with the described action made behind the scene.
JUSTIFICATION :
If the server is down, the end user will be quite surprised to see nothing on the screen, will say that the application does not work, and that's all. He will not be confident and will not buy.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
When the server is down, JWS would detect this after a 3 sec (for example) timeout and would launch the application from the cache.
ACTUAL -
My application runs with offline-allowed and <update check="timeout" policy="always"/>
When the server is down, the application is launched after a very long time (2 mn ?), which is a disastrous end user experience.
CUSTOMER SUBMITTED WORKAROUND :
Supposing that a user reports the problem, tell him to modify the jvm args (with javaws control panel), by adding -Dsun.net.client.defaultConnectTimeout=3000.
If this works, it is not a commercial solution.