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, Sep 08 '19 at 01:27
I should clarify, I am using the boost socket in non-blocking mode (I set non_blocking(true) — theactiveactor, Sep 09 '19 at 14:41

score 0 · Answer 1 · answered Sep 10 '19 at 00:26

0

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

answered Sep 10 '19 at 00:26

Tom Trebicky

638
1
5
11

Boost socket async_send: how does it handle ewouldblock?

1 Answers1