You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, lack of proper timeout support is a known issue. Note however that this is unrelated to SSL/TLS, so in your case it looks like the underlying TCP/IP connection already times out.
FWIW: Your OS will likely still implement a timeout for the socket, though we currently offer no API to change this value. It will likely be anywhere between a few minutes or hours, which is likely way beyond what most applications want.
explain why a write event is expected and what kind of write event is suppose to trigger this?
This is the normal async socket connection approach: Open the underlying socket resource, set it to non-blocking mode and start the connection. Once the socket descriptor becomes writable it means we can check if the connection has either been accepted or rejected.
Because we currently offer no custom timeout handling, we currently rely entirely on the OS timeout. This means the "write" event will actually trigger eventually, you're probably just not patient enough :-)
Activity
clue commentedon Dec 5, 2015
Yes, lack of proper timeout support is a known issue. Note however that this is unrelated to SSL/TLS, so in your case it looks like the underlying TCP/IP connection already times out.
FWIW: Your OS will likely still implement a timeout for the socket, though we currently offer no API to change this value. It will likely be anywhere between a few minutes or hours, which is likely way beyond what most applications want.
See also PR #51 for a possible implementation.
This is the normal async socket connection approach: Open the underlying socket resource, set it to non-blocking mode and start the connection. Once the socket descriptor becomes writable it means we can check if the connection has either been accepted or rejected.
Because we currently offer no custom timeout handling, we currently rely entirely on the OS timeout. This means the "write" event will actually trigger eventually, you're probably just not patient enough :-)
Let's look into finally getting #28/#51 in!