Detecting dead/crashed clients at the server.
- From: "Tino Donderwinkel" <tino@xxxxxxx>
- Date: Fri, 3 Oct 2008 22:53:01 +0200
I have written a simple client/server remoting app. The client connects to the servers object, and the server signals the client through an event.
This works perfectly. (Keywords here; Singleton, marshalling, events, Activator.GetObject(..))
The only problem is that when a client does not correctly 'disconnect' from the server, the server keeps trying to send an event to the client, even though the client is no longer there. This will 'lock' the server. Only restarting the server component will 'solve' the problem.
I have read many posts of other peope with the same problem, but I cannot really get a proper solution.
Preferrably, I would like to do something in the event method itself, and I do not really want to keep track of clients by having them register through a method, adding something to a hashtable. I think the framwork should be able to solve this by itself, right?
If someone has a proper solution, or can point me to the correct resources... awesome!
Tino
[Exchange] MVP
.
- Prev by Date: VPN error
- Next by Date: Some notes for .net developers, hope it's useful for you!
- Previous by thread: VPN error
- Next by thread: Some notes for .net developers, hope it's useful for you!
- Index(es):
Relevant Pages
|
Loading