boost-asio | 易学教程

How to create a thread pool using boost in C++?

阅读更多关于 How to create a thread pool using boost in C++?

How do I create a thread pool using boost in C++, and how do I assign tasks to the threadpool? Jeroen Bollen The process is pretty simple. First create an asio::io_service and a thread_group. Fill the thread_group with threads linked to the io_service. Assign tasks to the threads using the boost::bind function. To stop the threads (usually when you are exiting your program) just stop the io_service and join all threads. You should only need these headers: #include <boost/asio/io_service.hpp> #include <boost/bind.hpp> #include <boost/thread/thread.hpp> here is an example: /* * Create an asio:

Confused when boost::asio::io_service run method blocks/unblocks

阅读更多关于 Confused when boost::asio::io_service run method blocks/unblocks

问题 Being a total beginner to Boost.Asio, I am confused with io_service::run(). I would appreciate it if someone could explain to me when this method blocks/unblocks. The documentations states: The run() function blocks until all work has finished and there are no more handlers to be dispatched, or until the io_service has been stopped. Multiple threads may call the run() function to set up a pool of threads from which the io_service may execute handlers. All threads that are waiting in the pool

boost asio async_write : how to not interleaving async_write calls?

阅读更多关于 boost asio async_write : how to not interleaving async_write calls?

问题 Here\'s my implementation : Client A send a message for Client B Server process the message by async_read the right amount of data and will wait for new data from Client A (in Order not to block Client A) Afterwards Server will process the information (probably do a mysql query) and then send the message to Client B with async_write . The problem is, if Client A send message really fast, async_writes will interleave before the previous async_write handler is called. Is there a simple way to

What is the usefulness of `enable_shared_from_this`?

阅读更多关于 What is the usefulness of `enable_shared_from_this`?

问题 I ran across enable_shared_from_this while reading the Boost.Asio examples and after reading the documentation I am still lost for how this should correctly be used. Can someone please give me an example and/or and explanation of when using this class makes sense. 回答1: It enables you to get a valid shared_ptr instance to this , when all you have is this . Without it, you would have no way of getting a shared_ptr to this , unless you already had one as a member. This example from the boost

Why do I need strand per connection when using boost::asio?

阅读更多关于 Why do I need strand per connection when using boost::asio?

问题 I\'m reviewing HTTP Server 3 example on Boost\'s website. Could you guys please explain why I need strand per connection ? As I can see we call read_some only in handler of read-event. So basically read_some calls are sequential therefore there is no need for strand (and item 2 of 3rd paragraph says the same thing). Where is the risk in multi-threading environment? 回答1: The documentation is correct. With a half duplex protocol implementation, such as HTTP Server 3, the strand is not necessary

boost asio async_write : how to not interleaving async_write calls?

阅读更多关于 boost asio async_write : how to not interleaving async_write calls?

Here's my implementation : Client A send a message for Client B Server process the message by async_read the right amount of data and will wait for new data from Client A (in Order not to block Client A) Afterwards Server will process the information (probably do a mysql query) and then send the message to Client B with async_write . The problem is, if Client A send message really fast, async_writes will interleave before the previous async_write handler is called. Is there a simple way to avoid this problem ? EDIT 1 : If a Client C sends a message to Client B just after Client A, the same