S
sklett
I need to support "offline operation" - that is, if the DB server for
whatever reason is unavailable (network communication down, server crashed,
someone cut the users cat5, etc) I need to store the data locally until
communication is restored at which point I will catch-up on a worker thread
and update everything.
My problem is determining when the server is unavailable. I have tried to
come up with a clever process to catch events and exceptions that would
indicate loss of server availability, but they end up being a little too all
encompassing. In other words, I want avoid a bug on my part throwing an
exception and being treated as a server outage.
I guess I could resort to running Reg. Expressions on the exception message?
Have any of you had to implement something like this? If so, how did you
handle this?
Thanks,
Steve
whatever reason is unavailable (network communication down, server crashed,
someone cut the users cat5, etc) I need to store the data locally until
communication is restored at which point I will catch-up on a worker thread
and update everything.
My problem is determining when the server is unavailable. I have tried to
come up with a clever process to catch events and exceptions that would
indicate loss of server availability, but they end up being a little too all
encompassing. In other words, I want avoid a bug on my part throwing an
exception and being treated as a server outage.
I guess I could resort to running Reg. Expressions on the exception message?
Have any of you had to implement something like this? If so, how did you
handle this?
Thanks,
Steve