On 2/28/06, Wolfe, Stephen S GS-11 6 MDSS/SGSI
<Stephen.Wolfe AT macdill .DO.T af.mil> wrote:
>
> Without doing massive redesign (I use a DBC and remote views, they work
> good for me) how can I catch this disconnect and reestablish a
> connection with an appropriate user friendly message (feedback) to the
> user.
>
You're trying to solve a low-level problem (network drop-outs) in a
high-level language.
Ideally, you could get logs from a machine at the remote site and
document to the network administrators that they are getting ripped
off on their T-1. As Whil indicated in another thread, seven seconds
downtime in three years is more like the performance you are paying
for. There is a good chance that there is defective equipment (or
possibly network configuration) somewhere between there and there that
ought to be fixed. It's more likely to get worse than better.
If that's out of the range of possibilities, and you are a small cog
in a vast machine (I know the feeling), in your error handler, catch
these errors, pop up a huge form stating "LOSS OF NETWORK
CONNECTIVITY... RECONNECTING" and restart your application.
Okay, more practically, what is the error? Are you using a data
manager,so there's a central place to detect the error?
--
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com
©2006 Ted Roche |
