boost-asio

When using boost::asio for some asynchronous TCP communication I noticed it starts a lot of (3-4) internal threads. Reading in the documentation , it says "The implementation of this library for a particular platform may make use of one or more internal threads to emulate asynchronicity" Now my lib has very strict requirements to not start any extra threads (except one that is supplied by the client and which now starts io_service::run() ). Is there any way to stop boost::asio from creating these extra threads? Alternatively, is there any other async library out there that can run in only one

How do it clear all posted tasks which already queued in a io_service::strand ? I see no similar method from boost document. I have yet to find a need for it, as it can be resolved correctly with properly designing the asynchronous call chains. Generally, the Boost.Asio API is carefully designed in such a way that it prevents complex applications from becoming complicated in the asynchronous flow. If you have examined the call chains, and are absolutely certain that the effort to redesign them is a greater current and future risk than introducing the complication of clearing a strand, then

I had intended to have a thread in my program which would wait on two file descriptors, one for a socket and a second one for a FD describing the file system (specifically waiting to see if a new file is added to a directory). Since I expect to rarely see either the new file added or new TCP messages coming in I wanted to have one thread waiting for either input and handle whichever input is detected when it occures rather then bothering with seperate threads. I then (finally!) got permission from the 'boss' to use boost. So now I want to replace the basic sockets with boost:asio. Only I'm

Consider an echo server implemented using Boost.asio. Read events from connected clients result in blocks of data being placed on to an arrival event queue. A pool of threads works through these events - for each event, a thread takes the data in the event and echos it back to the connected client. As shown in the diagram above, there could be multiple events in the event queue all from a single client. In order to ensure that these events for a given client are executed and delivered in order, strands are used. In this case, all events from a given connected client with be executed in a

The title is my question. I already found a topic related to this here -> Using SSL sockets and non-SSL sockets simultaneously in Boost.Asio? and basically I'm in the same situation but for some reason I couldn't comment there and/or contact the questioner directly so I'm doing this as a new question. I have a set up ssl socket ssl::stream<ip::tcp::socket> socket_; where clients can connect just fine with socket_.async_handshake(ssl::stream_base::server, session::handle_handshake) and then read/write with async_write(socket_, buffer(send_data, send_length), session::handle_read) socket_.async