How to handle unexpected disconnect

Question

I've got a question concerning best practices with .NET remoting. The code is smelly and I need to do some refactoring.

The thing is: I've got multiple classes that derive from MarshalByRefObject and their data is used in the client software. Once the server disconnects I get RemotingException.

The bad thing about this is: My references to all the MarshalByRefObjects are all over the place (including but not limited to the GUI) and upon disconnection the exception turns up anywhere in my code.
Obviously I'd like to handle those exceptions in one place. Are there any best practices for this?

Essentially, I'd like to put together some sort of "offline" -mode for the client

Answer 1

设法通过使用代理设计模式来解决此问题