Boost socket async_send: how does it handle ewouldblock?

Question

On Unix, send() on a non-blocking socket could return error EWOULDBLOCK if outbound socket buffer is full. In this case, one should call select() to determine when it's possible to retry. Does Boost sockets in nonblocking mode handle all of this for you?

EWOUDLBLOCK only arises in non-blocking mode. Async mode is not non-blocking mode. It is akin to blocking mode on a separate thread. — user207421
I should clarify, I am using the boost socket in non-blocking mode (I set non_blocking(true) — theactiveactor

Tom Trebicky Tom Trebicky · Accepted Answer · 2019-09-10T00:26:18

Yes, it does. You can check for yourself for example here boost/asio/detail/impl/socket_ops.ipp.

Boost socket async_send: how does it handle ewouldblock?

1 Answers