[boost] [beast] write_some EWOULDBLOCK/EAGAIN error recovery non-blocking operations

Subject: [boost] [beast] write_some EWOULDBLOCK/EAGAIN error recovery non-blocking operations
From: Artyom Beilis (artyom.beilis_at_[hidden])
Date: 2017-07-03 20:10:47

Have been Beast tested with non blocking sockets?
I hadn't found a single reference to asio's non_blocking_io?

One of the common use cases is when I want to push a small message to
stream (chunk). In 99% of cases the operation will not block so I want
to handle this as an optimization for not returning to even loop and
creating a callback.

According to the reference I didn't find how write_some will behave? I
expect to get EWOULDBLOCK kind of error and start asynchronous
operation. However I didn't find any reference to the code to
non_blocking_io so I wonder if it is supported at all.

On same note - how do I run unit tests using b2 - Beast ins't fully
Boostified which BTW is also bothering me.

Artyom