I see no problems here. I use Idle and Connect timeouts in production (for
plain sockets), they work fine.
Protocol-specific components expose TWSocket members so user can add any
handlers he wants.
This option might seem slighly leaking abstraction but it will work just now,
without any
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
state.
> 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
