The question is how quickly the web site is likely to respond, not how fat your pipe connecting to it is. 3 seconds could easily be nowhere near long enough if the server is under heavy load.
You say you don't want to "delay the routine" if the web site is down, but you presumably don't wish to abort the routine just because the web site is a bit slow to respond. Depending on what the potentially-delayed-routine in question is doing, perhaps you could do your URL check in a background thread ? From: [email protected] [mailto:[email protected]] On Behalf Of Ross Levis Sent: Monday, 13 December 2010 16:19 To: 'NZ Borland Developers Group - Delphi List' Subject: [DUG] Indy ConnectTimeout/ReadTimeout recomendations I'm after minimum recommendations for ConnectTimeout and ReadTimeout for connecting to an HTTP URL. Assuming a DSL internet connection, could these be say 3 seconds each and not likely to abort too early in most cases? I'm executing HTTP.Head to determine if a URL is valid but I don't want to delay the routine too much if the website is down. Thanks.
_______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
