When an error is a valid response
Udi is talking about occasionally connected clients, and point to several challenges that you have to face when you are building such applications. One of the major issues with such clients is that you have to take into account the fallacies of distributed computing and how to deal with them.
But, and this is important, having to deal with those can be expensive in terms of time and complexity. There are many scenarios when telling the user that the system is not operational is a valid choice. No, it is not always valid, and there are as many application where you explicitly need to deal with that, but there are more when connectivity can be assumed and the only worry you have in this regard is handling the failure condition gracefully.
Comments
The easiest way to deal with the connectivity problems is to animate some hypnotizing controls in the UI (progress bars, AJAX spinner, etc.) while desprately trying to retry network operation.
Comment preview