in need a way of polling events but not executing handlers about asio

[mabrarov]

on some GUI programs, it's rather handy to have network IO and gui executed in the same thread.

What's the issue with this solution (generic solution not related to Asio):

1. keep Asio event loop in a dedicated thread pool (can be of one thread)
2. in Asio completion handlers just send events into main event loop (could be GUI event loop)

?

I did the same in ma_qt_echo_server by wrapping Qt signals with Asio completion handlers and using Qt::QueuedConnection type of Qt signal / slot connection.

[vinipsmaker]

// or call g_main_idle_add() to post an execution of io.poll()

...

// or just  g_main_loop_run()

If you want to integrate GTK+ and Boost.Asio event loops, check this: https://stackoverflow.com/questions/1001032/how-to-integrate-boost-asio-main-loop-in-gui-framework-like-qt4-or-gtk/66269341#66269341

The StackOverflow page has info on Qt as well (I haven't checked this one yet, but if it proves insufficient I'll offer my own solution later).