Yes, I think this is not a simple solution. In the past when I have
created a timer which times out before the network and then FTP.Abort
this caused me a problem with messages like "Component Not Ready", until
the whole thing had completed. So I have just left it all in its default
On 20/11/2017 10:25, Angus Robertson - Magenta Systems Ltd wrote:
ICS sockets have built-in timeout feature, just define
BUILTIN_TIMEOUT and use TimeoutIdle / TimeoutConnect / OnTimeout.
I suspect TimeoutConnect has never been tested, it is not implemented
in any ICS protocol components or samples.
Components like FTP would need the OnTimeout event to be added, which
would then try to abort the connection. This might be successful for
wsocket, but Windows will still be trying to connect until it's
internal timeout, and probably would not allow a second connection
attempt until the first had finished.
Timeouts are a fact of life with TCP/IP, and difficult to fight.
Because the built-in timeout stuff was not enabled by default until
2011, most protocol components and/or applications have their own
timeout implementations, and generally we don't mess with stable and
tested code, unless doing so adds significant benefits.
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be