Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Answer depends on type of your application. There are applications that can work offline - Microsoft Outlook for example. Such applications doesn't treat connectivity exceptions as critical, they can save your work locally and synchronize it later. Another applications such as online games will treat communication problem as critical exception and will quit if connection gets lost.</p> <p>As of error handling, I think that you should control exceptions on all layers rather than relying on some general exception handling piece of code. Your business layer should understand what happened on lower layer (data access layer in our case) and respond correspondingly. Connection lost should not be treated as <em>unexpected exception</em> in my opinion. For good practices of exceptions management I recommend to take a look at <a href="http://msdn.microsoft.com/en-us/library/cc309505.aspx" rel="nofollow noreferrer">Exception Handling Application Block</a>.</p> <p>Concerning application behavior, you should answer yourself on the following question "Does my application have business value for customer in disconnected state?" In many cases it would be beneficial to end user to be able to continues their work in disconnected state. However such behavior tremendously hard to implement.</p> <p>Especially for your scenario Microsoft developed <a href="http://msdn.microsoft.com/en-us/library/cc540753.aspx" rel="nofollow noreferrer">Disconnected Service Agent Application Block</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload