L
Lex
I have an app that allows for cross process eventing. I have a server
that instantiates a shared object that external processes can remotely
get a refernce to and register for events.
The problem I have is when one of the clients die uncleanly without
unregistering for the event. The remote object does not know that the
client is gone an still tries to call the delegate for that client.
This results in a socket exception after a few seconds.
Is there a clean way to deal with this? Is there a way to have the
remote object remove the dead client's delegate from the event's
Invocation list if it fails with a given exception?
Regards
that instantiates a shared object that external processes can remotely
get a refernce to and register for events.
The problem I have is when one of the clients die uncleanly without
unregistering for the event. The remote object does not know that the
client is gone an still tries to call the delegate for that client.
This results in a socket exception after a few seconds.
Is there a clean way to deal with this? Is there a way to have the
remote object remove the dead client's delegate from the event's
Invocation list if it fails with a given exception?
Regards