> What about enabling TCP keep-alive and timeout? > ICSv7 TWSocketServer has these properties!
My experience is that many topologies do not work reliably using those features. The best way is really to use an application level ping command as I explained. -- [email protected] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ----- Original Message ----- From: "Fastream Technologies" <[email protected]> To: "ICS support mailing" <[email protected]> Sent: Tuesday, January 13, 2009 9:40 AM Subject: Re: [twsocket] Detect 'dead' clients > What about enabling TCP keep-alive and timeout? ICSv7 TWSocketServer has > these properties! > > Regards, > > SZ > > On Mon, Jan 12, 2009 at 8:13 PM, <[email protected]> wrote: > > > Hello, > > > > I am using the TWSocketServer (Server) component to which several TWSocket > > components connect (Client), > > I successfully capture the event when the client gets disconnected > > however I am running into a problem in the case where a client is > > abnormally terminated, user ends task in task manager. > > How can my TWSocketServer component know that the client is not there > > anymore ? > > I cannot do a ping because several clients might display the same ip (NAT) > > > > Any help would be greatly appreciated - > > > > Thanks > > -- > > To unsubscribe or change your settings for TWSocket mailing list > > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > > Visit our website at http://www.overbyte.be > > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
