socketTimeoutInterval is NOT for connecting

[RCS]

  I use 'socketTimeoutInterval' quite often...but that is for reading and
writing to a socket that is already open. I am looking for a timeout setting
for 'connecting' to a socket. If I use 'open socket' to connect to a device
that is either offline (or invalid), I would like to set a time out of 5 or
10 seconds (the device usually responds in 1) instead of the default 1
minute. I can only get so many cups of coffee in a day you know...

Of course, I may be missing something  ;-)

You may reprimand me at your leisure...

JR


> Date: Mon, 28 Oct 2002 00:17:30 +0100
> From: Pierre Sahores <psahores at easynet.fr>
> To: metacard at lists.runrev.com
> Subject: Re: Invalid socket connect timeout?
> Reply-To: metacard at lists.runrev.com
>
> RCS a écrit :
> >
> >   Is there a way to set the time that the internal MetaCard engine takes
to
> > 'try' to open a socket? I have found that if a socket is not valid (or
the
> > host is not on the network) MetaCard will try to connect for up to one
> > minute until it returns a socketError...is this normal?
> >
> > Thanks,
> > JR
> >
>
> Try >> set the socketTimeoutInterval to "10"
> --
> Cordialement, Pierre Sahores
>