Hi Ken,Tim,
Quick question for you.
Is there an intention to make this timout more user-friendly, i.e. maybe the ORB or ACC pop a window to the user telling him/her that there is currently a communication error, would you like to retry, something like that... Right now, if you don't have your console open, you have no idea what is going on...is the network or server down or just really slow? The user just doesn't know.
The default behavior I'm noticing on b50 is that an Application Client (started with WebStart) just keeps retrying while logging its problem in the console. From the user's point of view, there's nothing happening (I suspect typical users will NOT have their Webstart console opened, or if they do, I doubt they would go through the stack traces to understand what is happening).
I'll be happy to file an RFE for this, I just didn't want to do that if it's already on the roadmap.
Francis
[Message sent by forum member 'chiss' (chiss)]
http://forums.java.net/jive/thread.jspa?messageID=221927