In a client-server relationship, should the server always rethrow the exception to the client?

There are more than one type of error. For errors that the client can correct and retry, give them instructions on what to correct. For other errors, where retrying will make no difference, such as an unauthorized action, let the user know why they can't perform the action, and if there's anything they can do to change the matter.As you suggested, if the client issues a request to update the record, and something on the server, out of the control of the client, occurs, but the server can recover, then don't notify the client.

If you need to know, then have the server notify you. If the error occurs on the server, but the server isn't able to recover, you definitely need to notify the client of the failure and to either notify you, or try again later. Again, the system should notify you.

That particular error sounds like a configuration problem on the server, so the client doesn't have any means of action and shouldn't be given that information. I generally cover that kind of error under a generic error message ("System error, please contact your system administrator") and log the error on the server (for later inspection).

The client does have means of action if the client supplies the path as a parameter. Otherwise, I totally agree. The best bet would be to write to the most reliable place (isolated storage?), so I guess you are pretty much spot on.

– dotnetdev Jun 1 '10 at 22:12 Agreed with the case where the client supplies the path. – Flavius Stef Jun 1 '10 at 22:27.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.