Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: KA9Q question Message-ID: Date: 9 Jan 91 21:35:02 GMT References: <1991Jan9.183444.14852@magnus.ircc.ohio-state.edu> Sender: @grape.ecs.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: /home/sun.soe/ecs/nelson/.organization Lines: 31 In-Reply-To: mirza@magnus.ircc.ohio-state.edu's message of Wed, 9 Jan 91 18:34:44 GMT In article <1991Jan9.183444.14852@magnus.ircc.ohio-state.edu> mirza@magnus.ircc.ohio-state.edu (Khalid Mirza) writes: I am using the KA9Q Internet Protocol Package at The Ohio State University for developing an internet FAX facility for IBM PCs. I have the following question about the software: While trying to establish a TCP socket connection, the "connect" routine does not time-out if the socket listener on the other end is not running. Is there any way to include the time-out feature, in order to break from the socket connect routine after a certain length of time if the connection is not established? Why would you want to? There are only two reasons I know of to cancel a connection, once started: 1) If you run out of resources, and suspect that the resources tied up by not-yet-established connections could be put to better use by other potential connections, 2) If you decide to withdraw the connection. For example, you sent hate mail to karn@ka9q.bellcore.com about his avoidance of timeouts, and you became convinced that timeouts were indeed bad, then you would want to cancel that piece of mail. But really, neither of the above are real "timeouts", in the sense that neither waits a fixed period of time before wimping out. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600 It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.