"Michael Stieler" <michael.stieler@rie.eu> wrote in message
news:479d9b66$1@newsgroups.borland.com...
> Is it also okay to be raised when Connecting a IdTcpClient and
> getting a ConnectTimeOut ? It seems that the 10038 Exception is
> internally catched and converted into a TimeOutException, because
> this is what my program reports.
Blocking sockets do not support timeout at the OS level when connecting to a
server. So when Indy's Connect() times out, Indy closes the socket in order
to force the OS to stop waiting immediately. That is what you are seeing
happen. The actual exception occurs within the context of a worker thread
that Connect() uses internally, so you will not see the 10038 exception
reach your code.
Gambit
