Remy Lebeau (TeamB) wrote:
> "Krzysztof Kozłowski" <kozlorf@poczta.onet.pl> wrote in message
> news:44e37bbf$1@newsgroups.borland.com...
>
>> Now I see, that in Indy 10 one cannot call the Connect() method
>> with the timeout parameter.
>
> That is because it was moved to a property.
>
>> I tried to set the ConnectTimeout value for the client, but it
>> seems that it's not working anymore.
>
> Yes, it does. Connect timeouts work the same in Indy 10 as they did in Indy
> 9. The desired value is simply coming from a property now instead of from a
> method parameter.
>
>> Could anyone please help me, telling how to apply the timeout
>> to TIdTcpClient.Connect()?
>
> You already know the answer to that - use the ConnectTimeout property.
>
>
> Gambit
>
>
Indeed it works. I thought, that the Connect() function just exits after
the timeout elapsed, but it seems it gives a timeout exception instead.
Big thanks,
Krzysztof Kozlowski
