Hello,
Real quick question.
It is my understanding that THttpCli does not timeout.
Say, it has connected to the web server and sent the request.
But if the server doesn't send anything back, THttpCli will
not timeout. Am I correct?
--
Best regards,
Jack
--
To unsubscribe or change your
Hello Jack,
real quick answer :)
correct !
Winsock will timeout after a while, but this is depending on many
factors and can take a long time. For automated aplications use your own
timeout.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Thank you Wilfried and Arno for the real quick replies :)
Winsock will timeout after a while, but this is depending on many
factors and can take a long time. For automated aplications use your own
timeout.
Any idea how long it can be? Like, a few minutes? or hours?
Real quick question.
It
Hello Wilfried,
I wonder why would winsock even time out in this case?
Isn't it legitimate to have a socket connected and doing nothing?
--
Best regards,
Jack
Wednesday, October 26, 2005, 1:35:36 PM, you wrote:
Hello Jack,
real quick answer :)
correct !
Winsock will timeout after a
Hello Jack,
I wonder why would winsock even time out in this case?
Isn't it legitimate to have a socket connected and doing nothing?
Yes of course. As always I anser to fast without carefully reading the
request :( If yoiu connect and do nothing noone will timeout of course,
unless the server
It is my understanding that THttpCli does not timeout.
Say, it has connected to the web server and sent the request.
But if the server doesn't send anything back, THttpCli will
not timeout. Am I correct?
TCP/IP has timeouts for opening a connection, although not usually once
the connection
