Francois PIETTE wrote: >> I just wonder how other programs can provide a >> user defined TCP timeout that appears to overrule the system setting or >> is something like that just a fake? > > I've searched on MSDN and found that setsockopt has those options: > SO_RCVTIMEO Receives time-out in milliseconds (available in the Microsoft > implementation of Windows Sockets 2). > SO_SNDTIMEO Sends time-out in milliseconds (available in the Microsoft > implementation of Windows Sockets 2). > > Maybe this is what you search for ?
Probably yes. But they say not much about SO_RCVTIMEO. "SO_RCVTIMEO and SO_SNDTIMEO When using the recv function, if no data arrives during the period specified in SO_RCVTIMEO, the recv function completes. In Windows versions prior to Windows 2000, any data received subsequently fails with WSAETIMEDOUT. In Windows 2000 and later, if no data arrives within the period specified in SO_RCVTIMEO the recv function returns WSAETIMEDOUT, and if data is received, recv returns SUCCESS." Hmm, that's a bit confusing concerning the win-versions (wasn't WS 2 available on NT4 as well?). > The text is not clear is those BSD options are supported or not ! If you mean "supported or not by different OS" I agree, unless this won't be totaly clear I won't use it. However it appears that those options could be used to substitute own timeout implementations completely, correct? Arno Garrels -- 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
