Richard Hodges

Where `e` is any executor, which can also be a strand.

https://www.boost.org/doc/libs/1_77_0/libs/beast/doc/html/beast/using_io/asio_refresher.html

>Concurrency I/O objects such as sockets and streams are not thread-safe. Although it is possible to have more than one operation outstanding (for example, a simultaneous asynchronous read and asynchronous...

This is an async full-duplex client in the same demo repo. Note the use of dispatch to marshall work onto the correct _executor_. https://github.com/test-scenarios/boost_beast_websocket_echo/blob/master/pre-cxx20/chatterbox/connection.cpp#L125

For the record, this is almost certainly un-necessary: > I have 4 threads handling io_ctx completion If all your I/O is going through one network card, it is 99.9999% un-necessary....

> Ok. Got it. Let me try the dispatch. I was using beast's bind_front_handlers but ur code seems to be using boosts bind APIs so my code may beed some...

Thank you for the detailed description. I would like to duplicate this locally. May I ask you to supply a 1-page go program to act as a test server so...

I have investigated this. The problem seems to be a non-conformance in Beast (the inability to set the window bits parameters without an `=` value) coupled with a poorly configured...

Thanks for the heads -up @markus-bonk . Is there a particular reason you are looking to use the system_executor in preference to an io_context::executor_type? I only ask because there are...

Sorry misread the question. Original answer is below. Which error is being reported for you when the client truncates the websocket stream? ---- Hmm. We actually go to some lengths...