I'm building a client/server application that needs reasonably rapid
user response time. Specifically, if I attempt to connect() to a
"sick" machine, I don't want the user to be sitting there for the
standard 75 (or so) second connect() timeout interval.
The setsockopt() manpage talks about a couple of settable socket
parameters that would seem to be the answer to my problem:
SO_SNDTIMEO and SO_RCVTIMEO
I note that the documentation of these items in the manpage is somewhat
skimpy. Also, they do not appear to actually do what I want, which is
to reduce the 75 second timeout interval to something more reasonable
(for my application). (setsockopt changes the values all right, and
getsockopt reports them, but the actual timeout interval remains
unchanged.)
Question 1. Are these the correct parameters to use to change the
timeout interval?
Question 2. If the answer to (1) is no, how do I reduce this timeout
interval?
Question 3. Where can I find a more complete explanation of the purpose,
effect, and valid range of values for SO_SNDTIMEO and
SO_RCVTIMEO?
Please note that I am running this under DU 4.0.
I also seek answers to the above questions relative to DU 3.2 (which we
also are running). We will have to run this under 3.2 for a while yet,
so I also need a solution that release also.
Thanks in advance,
--
John G Dobnick "Knowing how things work is the basis
Information & Media Technologies for appreciation, and is thus a
University of Wisconsin - Milwaukee source of civilized delight."
jgd_at_csd.uwm.edu ATTnet: (414) 229-5727 -- William Safire
Received on Thu Oct 03 1996 - 01:19:28 NZST