471,582 Members | 1,529 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,582 software developers and data experts.

Advice on actor/observer pattern

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
object.

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
case?

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.

Thanks.

May 23 '06 #1
0 974

This discussion thread is closed

Replies have been disabled for this discussion.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.