> > What I need is a way for the user-code to yield, and then resume later when > > it has the info it needs to build the response.
> I used beast::websocket to keep the https connection open with a client and > used boost::asio::post() on the server. This way, a worker thread on the > server can submit a job for processing and go listen for new incoming > requests. Some worker thread will be called-back to run a completion function > when the response is ready. Yeah, I didn't know about boost::asio::post() until yesterday. Looks like this is the way, thanks. > Please review http_server_async.cpp and websocket_server_async.cpp files in > the examples page. Will do. Loup. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
