By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,485 Members | 1,031 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,485 IT Pros & Developers. It's quick & easy.

Advice on actor/observer pattern

P: n/a
I have the actor/observer pattern implemented in my application. I have
added a remoted object as an observer to an actor object. In other
words, a proxy object (returned by the Activator.GetObject()) is a
listener to some actor object which unpredictably calls some method
from proxy object's interface. The remoted object is a long-living

The question is whether this is reliable or not? Since the logical
validity of the listener object depends on the state of the proxy-stub
objects and their ability to communicate, if the communication medium
becomes unreliable the proxy-stubs cannot communicate and the listener
becomes invalid.

Will an invalid remoted object throw exceptions in this case?

Will an invalid remoted object try to automatically reconnect in this

Should I use the decorator pattern to encapsulate this remoted object,
and handle re-connections, or is there some other mechanism?
NOTE: I am porting from .NET 1.1 and want to make maximal use of all
..NET 2 API's/design patterns. I am looking for 'best design' solutions
of these kinds of problems.


May 23 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.