#1310 closed Feature Request (Fixed)
TCPConnect Timeout
| Reported by: | Proggy | Owned by: | |
|---|---|---|---|
| Milestone: | Future Release | Component: | AutoIt |
| Version: | Severity: | None | |
| Keywords: | Cc: |
Description
I'd like the TCPconnect() function to have a parameter where you can specify the timeout before stopping the connection attempt.
The current TCPConnect function is as follows:
TCPConnect(IPAddr,port)
If IPAddr or port is unavailable/closed then the connection attempt only times out after 5-10 secs. What I want is the ability to set the timeout (in ms)
ex:
TCPConnect(IPAddr,port[,timeout])
Thanks
Hawk
Attachments (0)
Change History (8)
comment:1 Changed 14 years ago by anonymous
comment:2 follow-up: ↓ 5 Changed 14 years ago by Jpm
Ther is a fix in the pipe that is going to do the same timeout as for other TCP...() functions.
Is that OK?
comment:3 Changed 14 years ago by Jpm
- Resolution set to Fixed
- Status changed from new to closed
Fixed with ticket #1573
comment:4 Changed 14 years ago by TicketCleanup
- Milestone set to Future Release
Automatic ticket cleanup.
comment:5 in reply to: ↑ 2 ; follow-up: ↓ 6 Changed 14 years ago by bjoern@…
Replying to Jpm:
Ther is a fix in the pipe that is going to do the same timeout as for other TCP...() functions.
Is that OK?
I don´t understand what you meaning with this sentence. I have the problem too and i don´t know the resolution...
mfg bjoerni
comment:6 in reply to: ↑ 5 ; follow-up: ↓ 7 Changed 14 years ago by Jpm
Replying to bjoern@…:
Replying to Jpm:
Ther is a fix in the pipe that is going to do the same timeout as for other TCP...() functions.
Is that OK?
I don´t understand what you meaning with this sentence. I have the problem too and i don´t know the resolution...
mfg bjoerni
I mean that today we have already a timeout defined by Opt("TCPTimeOUT", ...) which is working with other TCP...() functions.
What I did is to use the same timeout for TCPConnect() too.
comment:7 in reply to: ↑ 6 ; follow-up: ↓ 8 Changed 14 years ago by anonymous
Replying to Jpm:
Replying to bjoern@…:
Replying to Jpm:
Ther is a fix in the pipe that is going to do the same timeout as for other TCP...() functions.
Is that OK?
I don´t understand what you meaning with this sentence. I have the problem too and i don´t know the resolution...
mfg bjoerni
I mean that today we have already a timeout defined by Opt("TCPTimeOUT", ...) which is working with other TCP...() functions.
What I did is to use the same timeout for TCPConnect() too.
so you plan to implement this in the future? or is it already included in the beta?
comment:8 in reply to: ↑ 7 Changed 14 years ago by Jpm
Replying to anonymous:
Replying to Jpm:
Replying to bjoern@…:
Replying to Jpm:
Ther is a fix in the pipe that is going to do the same timeout as for other TCP...() functions.
Is that OK?
I don´t understand what you meaning with this sentence. I have the problem too and i don´t know the resolution...
mfg bjoerni
I mean that today we have already a timeout defined by Opt("TCPTimeOUT", ...) which is working with other TCP...() functions.
What I did is to use the same timeout for TCPConnect() too.
so you plan to implement this in the future? or is it already included in the beta?
Yes, it is in the next beta or Release
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
i also have same problem
The result: Connect Failed! time-consuming: 20.9968sec
====
Opt("TCPTimeout",10)
Global $out_txt
TCPStartup()
$iBeginTime = TimerInit()
$socket = TCPConnect("192.168.1.18", 8080)
If $socket <> -1 Then
Else
EndIf
TCPCloseSocket($socket)
ConsoleWrite($out_txt & @CRLF)
MsgBox(0, "", $out_txt)