|
|
|
|||||
|
avoiding ping()ing to determine client's lifetime
Given two objects where one acts as a server to the other, is there a more elegant way to find out if a client has left other than regular ping()ing? Watching the Ice.Trace messages, I see that ICE rt knows when the tcp socket is closed, though I know there are other complex workings that wouldn't make it so straightforward.
The situation I want to handle is when a client crashes and is not able to send a logoff() type message. I apologize if I missed this in the documentation, I looked for a while. |
|
||||||
|
See Marc's answer on similar questions:
Client Disconnect Callback IceStorm error reporting hook Let us know if this doesn't fully answer your question though! Cheers, Benoit. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| How to determine the reason of a destroyed session | joel vennin | Help Center | 3 | 08-10-2006 09:19 PM |
| about avoiding to kill server by icegridnode reconnection | ChenQingQing | Help Center | 1 | 07-03-2006 04:32 AM |
| determine messagesize during runtime | DeepDiver | Help Center | 3 | 01-26-2006 08:22 AM |
| About the Proxy's lifetime | level | Help Center | 2 | 11-22-2005 09:34 AM |
| servant lifetime | nsns | Help Center | 1 | 11-05-2004 08:04 AM |