Yuval Ronen wrote:
1. The "Proactor" page has Advantages/Disadvantages section, but it doesn't specify in comparison to what (advantages and disadvantages are always compared to something). I'm getting the impression that it's compared to the Reactor approach. Is this correct?
Actually it is compared to both the Reactor and thread-per-connection approaches.
2. The "Platform-Specific Implementation" page notes that when using select/epoll/kqueue, demultiplexing is performed in one of the threads that calls boost::asio::io_service::run(). I assume that when this thread is awaken to perform some task, one of the other threads that called run() on the same boost::asio::io_service takes it position as waiting on select/epoll/kqueue. Is this correct?
Yes, that's correct.
3. ... So I guess that if I resolve() rather than async_resolve(), then no thread is created, and the actual resolving is done in the thread that called resolve()?
That's also correct. Thanks for the suggestions. I will add the clarifications to the documentation. Cheers, Chris