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, gaetan.s...@gmail.com 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
Re: [twsocket] Detect 'dead' clients
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. -- francois.pie...@overbyte.be Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be - Original Message - From: Fastream Technologies ga...@fastream.com To: ICS support mailing twsocket@elists.org 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, gaetan.s...@gmail.com 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
Re: [twsocket] Detect 'dead' clients
What kind of feature mechanism can you suggest for a TCP tunnel proxy then? On Tue, Jan 13, 2009 at 12:59 PM, Francois Piette francois.pie...@skynet.be wrote: 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. -- francois.pie...@overbyte.be Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be - Original Message - From: Fastream Technologies ga...@fastream.com To: ICS support mailing twsocket@elists.org 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, gaetan.s...@gmail.com 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
Re: [twsocket] Detect 'dead' clients
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. What kind of feature mechanism can you suggest for a TCP tunnel proxy then? Do you control both ends of the tunnel ? -- francois.pie...@overbyte.be Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) 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
Re: [twsocket] Detect 'dead' clients
Hello Francois, Well the tunnel client and server is ours but it has 4 ends. TCPClient--Internet--TunnelSSLClient--Internet--TunnelSSLServer-Internet--TCPServer Regards, SZ On Tue, Jan 13, 2009 at 5:23 PM, Francois Piette francois.pie...@skynet.bewrote: 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. What kind of feature mechanism can you suggest for a TCP tunnel proxy then? Do you control both ends of the tunnel ? -- francois.pie...@overbyte.be Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) 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
Re: [twsocket] Detect 'dead' clients
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. What kind of feature mechanism can you suggest for a TCP tunnel proxy then? Do you control both ends of the tunnel ? Well the tunnel client and server is ours but it has 4 ends. TCPClient--Internet--TunnelSSLClient--Internet--TunnelSSLServer-Internet--TCPServer OK, then it is not very difficult to implement a command the client will periodically send to the serveur. The server will simply remove that command from the data flow. Maybe you know Midware ? It implement a datagram feature which is the kind of thing you can use to implement a kind of ping. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) 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
Re: [twsocket] Detect 'dead' clients
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 - The only real solution is to implement a kind of ping in your application. The client periodically send a ping (not ICMP, just a kind of message) to the server using the connection. The server evaluate a timeout and disconnect any client not having sent their ping. Also you can implement a simple timeout: if a client has no sent any command or data for a given time, the server disconnect automatically. How to implement that depends on your application. There is no rule ! -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) 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
