https://www.boost.org/doc/libs/1_71_0/libs/beast/doc/html/beast/using_websocket/timeouts.html says

The timeout features of the TCP or basic stream should not be used when working with a websocket stream.

and

`The timeouts on the websocket stream are incompatible with the timeouts used in the tcp_stream. When constructing a websocket stream from a tcp stream that has timeouts enabled, th

I can see that ValidateReply() is called on a reply in RequestImpl.cpp's GetReply(Context&), and if the result's status_code falls outside of accepted range, the appropriate RequestFailedWithErrorException is thrown.

However, RequestFailedWithErrorException only includes the reply's HttpResponse, which may be excluding some very useful information. It would be really helpful if **

My app is multithreaded and any thread can arbitrarily make an RPC or publish info.

Are transmissions automatically serialized on a common asio strand? At the moment I require that all transmissions be queued and have a thread that does nothing but pop requests from the queue and send them to websocket-cpp. I would love to simplify this code if this queueing process is redundant.

On the ca

The first example in the USAGE section of the README.md does not compile. To wit, it is not clear which files must be #include'd in order to get it t run. After cycling through quite a different number of compile errors and header combinations, I got stuck here:

BeastHttp$ g++ --std=c++14 -Wfatal-errors -I./include -I../moetsi/dependencies/boost server.cpp -o runserver
In file included fr

Boost.Coroutine is, clearly, an extremely powerful framework. However, I am in a situation where adopting Boost.Coroutine is not currently an option.

I would like to see examples that don't use coroutines, that accomplish similar things to what's found here: https://github.com/yandex/ozo/blob/master/examples/request.cpp

For my situation, I am attempting to use OZO to replace libpqxx. Both OZ

Documentation states, that it's possible to use drop_result as part of the parsing policy: https://github.com/basiliscos/cpp-bredis#parse_result_titerator-policy

However, it's pretty unclear how to use it with the Connection object.

I read through the source code and Connection seems to be have hard-coded keep_result as policy type. How would I use drop_result with Connection objec

gaia looks great, but needs some docs. Can you provide a bit more helpful documentation on how to use it? Thanks.

Some ideas about docs:

• more info about fibers
• how to use with/without docker
• deploying into some cloud service (like GCE or Amazon)
• RPC usage example for microservices
• HTTP REST server usage example (PUT request, DELETE request, e.t.c.)
• comparison with other soluti