06-06-2014, 05:57 PM
Hi -
I know how to trap timeouts in TcpSocket.Send() using TcpSocket.Recieve() - but I'm also getting timeout errors on TcpSocket.ClientConnect().
The root cause of this is that the DNS at my institution is a mess. I have a fallback mechanism where the IP addresses are cached in a local database and if there is a timeout on ClientConnect() it will look up the IP address in the database. While this is a complete kludge - it works well except that it can take 10-15 seconds for the initial timeout. Is there a mechanism for setting the timeout of the initial connection lower?
Thanks
I know how to trap timeouts in TcpSocket.Send() using TcpSocket.Recieve() - but I'm also getting timeout errors on TcpSocket.ClientConnect().
The root cause of this is that the DNS at my institution is a mess. I have a fallback mechanism where the IP addresses are cached in a local database and if there is a timeout on ClientConnect() it will look up the IP address in the database. While this is a complete kludge - it works well except that it can take 10-15 seconds for the initial timeout. Is there a mechanism for setting the timeout of the initial connection lower?
Thanks