When the server is shutdown or is building rebooted, the
clients go into a loop of exception reports. Exception
messages should be made more user friendly.
I just moved the code from New into a new subroutine that
has a try/catch for Socket exception (what it gets when it
can't connect). If it throws, I make visible a "reconnect"
button which will retry the connect code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
More follow-up... In my copy, I also had to add a catch in
the stateTimer for server socket connection exceptions to
disable the polling if the server goes down during execution
rather than not being up before startup. And added a
message for a bad "config" exception to the start as well.
Then, I added disabling the server interactive buttons while
the polling is paused. All in the updated
Logged In: YES
user_id=590836
Here is my correct to squash this one -
http://www.knology.net/~meyweb/hippoclient.zip
I just moved the code from New into a new subroutine that
has a try/catch for Socket exception (what it gets when it
can't connect). If it throws, I make visible a "reconnect"
button which will retry the connect code.
Logged In: YES
user_id=590836
More follow-up... In my copy, I also had to add a catch in
the stateTimer for server socket connection exceptions to
disable the polling if the server goes down during execution
rather than not being up before startup. And added a
message for a bad "config" exception to the start as well.
Then, I added disabling the server interactive buttons while
the polling is paused. All in the updated
http://www.knology.net/~meyweb/hippoclient.zip
Logged In: YES
user_id=590836
Hey, check out the patch section. I am just learning my way
around Source Forge... I uploaded the patch there so you
don't have to go to my web site.