[DUG] Indy timeouts

[Jeremy Coulter]

That doesn't work! Theres HEAPS of posts on threads etc. about how it
doesn't work...I take that back, it DOES work, it something else that holds
it up.

I have solved the issue by using 2 threads. One instantiates the thread that
will do the HTTP GET and also acts as a timeout timer. If the time out is
reached it terminates the instantiated thread. Works well enough for me.

 

Jeremy

 

From: delphi-bounces at listserver.123.net.nz
[mailto:delphi-bounces at listserver.123.net.nz] On Behalf Of Ross Levis
Sent: Wednesday, 8 January 2014 5:36 p.m.
To: 'NZ Borland Developers Group - Delphi List'
Subject: Re: [DUG] Indy timeouts

 

There is a ConnectTimeout published property you can set.

 

From: delphi-bounces at listserver.123.net.nz
<mailto:delphi-bounces at listserver.123.net.nz>
[mailto:delphi-bounces at listserver.123.net.nz] On Behalf Of Jeremy Coulter
Sent: Wednesday, 8 January 2014 2:31 p.m.
To: NZ Borland Developers Group - Delphi List
Subject: [DUG] Indy timeouts

 

Hi All. I have an app. that I have to use Indy for that is just for an HTTP
GET.

It all works fine, however, if the device for the IP address I am trying to
access is not available, then I get the whole wait for 20 seconds for it to
time out issue thats not an indy problem, its the Windows tcp stack or
something apparently.

 

I am just wondering how others have solved this issue in the past etc.

 

 

Thanks, Jeremy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20140108/defb019a/attachment.html