how to capture the "client droped" exceptions?

in Help Center
Hello,
I took notice of the exceptions throwed by the Ice in the server-side if a client droped and did not destory its communicator(that means the client did not quit gracefully).
The exception output on my console are something like:
04/11/07 00:29:04.313 warning: connection exception:
TcpTransceiver.cpp:297: Ice::ConnectionLostException:
connection lost: WSAECONNRESET
local address = 172.196.4.101:1532
remote address = 172.196.4.101:1527
I'm wondering how to capture these exceptions since I want to do some additional process.
Cheers
Pierre.Siron
I took notice of the exceptions throwed by the Ice in the server-side if a client droped and did not destory its communicator(that means the client did not quit gracefully).
The exception output on my console are something like:
04/11/07 00:29:04.313 warning: connection exception:
TcpTransceiver.cpp:297: Ice::ConnectionLostException:
connection lost: WSAECONNRESET
local address = 172.196.4.101:1532
remote address = 172.196.4.101:1527
I'm wondering how to capture these exceptions since I want to do some additional process.
Cheers
Pierre.Siron
0
Comments
The correct way to handle this is with sessions, and session timeout. See demo/Ice/session for an example of how to do this.