Richard Hodges

Just to be clear about this, you must not initiate another async_write before the execution of the completion handler of the previous async_write.

Are you able to share a minimal working example that demonstrate the problem please? this is not behaviour we have observed.

@chriskohlhoff Any Ideas?

> > @chriskohlhoff Any Ideas? > > I did post the same in that repo as well. Havent seen reply :( Chris is a busy guy.

Great, thanks for letting me know.

I think a good start would be to set up a test that sets up the above scenario. Then place a breakpoint in the code for the async operation for...

waiting on the future is preventing progress of the io context. Simply invoke async_close with an empty lambda. The currently running async_read will complete with an error (websocket::error::closed) and any...

Reconnect on fail is best done by implicitly dropping the connection object and creating a new shared connection object. The implicit drop will happen when the last handler (containing the...

the `use_future` token causes the asynchronous initiation function to return a future, who´s value will be set when an the asynchronous operation completes. In order to complete, it must make...

Try: buffers_to_string(buffer.data())