Perhaps the TCP connection has some end-to-end keep-alive packets sent which does not leave the stream "idle"?
Regards, SZ ----- Original Message ----- From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Friday, March 02, 2007 3:36 PM Subject: Re: [twsocket] Don't trust routers! > It's an idle time-out yes. > > Fastream Technologies wrote: >> We -in our code- implement/interpret a connection timeout as "idle >> timeout". Could this be the case in Lancom as well? >> >> Best Regards, >> >> SZ >> >> ----- Original Message ----- >> From: "Arno Garrels" <[EMAIL PROTECTED]> >> To: "ICS support mailing" <twsocket@elists.org> >> Sent: Friday, March 02, 2007 2:31 PM >> Subject: [twsocket] Don't trust routers! >> >> >>> i.e. Lancom, I was told that it has an option ConnectionAge to >>> specify a connection time-out. According to the manual the >>> connection will be closed when the timeout expires. But nothing like >>> that happened. Instead, after the time-out expired a client >>> application happily sent data that was never acknowledged. >>> >>> --- >>> Arno Garrels [TeamICS] >>> http://www.overbyte.be/eng/overbyte/teamics.html >>> >>> >>> -- >>> 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 -- 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
