Markus, why not implementing some kind of NOOP over the protocol? Means that your client's sending some special small data packets over the line which the server simply drops, only if transfer is idle and possibly timer based?
Michael > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, February 14, 2007 3:38 PM > To: twsocket@elists.org > Subject: [twsocket] OnSessionClosed > > > Hello, > > strange problem here: > > - two PCs connected via normal LAN > - one runs my server app (simple TWSocket since the server > only has to handle one connection) > - the other one runs my client app (twsocket as well) > - the connection is a TCP connection > > Normal communication is fine. I've assigned OnSessionClosed > on both server and client side. > If I plug out the cable the server side detects the > OnSessionClosed, but not the client side! > > This also happens with the included demo programs Client5 and > TCPSvr. The server will recognize > the lost connection but not the client. Since I'd like to > reestablish that connection if there > hasn't been a request of my client program to close the > connection (I've implemented something > for that in my protocol) I need to know on the client side > when the connection is lost! > > What's wrong here? > > Greetings > > Markus > > > ebm-papst St. Georgen GmbH & Co. KG > Kommanditgesellschaft Sitz St. Georgen > Amtsgericht Freiburg HRA 601094 > Persoenlich haftende Gesellschafterin: > Papst-Motoren GmbH, Sitz St. Georgen > Amtsgericht Freiburg HRB 600163 > Geschaeftsfuehrer: Dr. Gerhard Lahm, Thomas Wagner > > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
