Hi<br><br>I would like to migrate an application from using Glib::Source (glibmm event loop) to use io_service instead.<br><br>The application is using glib::sources for two job:<br>- Drive lots of network IO connection<br>
- Process internal event which are generated in side the application it self.<br><br>The Io part is easy to fit into asio, but I&#39;m having problems seeing what the best way is to implement the core application event processing.<br>
<br>Using glib::source I could register an interface where two function is called:<br><br>bool prepare (int &amp;timeout);<br>bool dispatch (sigc::slot_base *slot);<br><br>Prepare could set a time out identifying how much time should elapse before dispatch is ready to process an event.<br>
<br>When the time is passed, the glib main loop will call the dispatch function, where I then can process the internal events.<br><br>How can this be implemented in boost::asio io_service?<br><br>I have look at the section 7.5 in <a href="http://en.highscore.de/cpp/boost/asio.html">http://en.highscore.de/cpp/boost/asio.html</a> but he is using a thread and a blocking call. Using a thread is not a solution in my case.<br>
<br>I would rather like either polling, or some kind of scheduling...<br><br>I any body has some hints, examples, advices it would be most appreciated.<br><br>--<br>Allan W. Nielsen<br><br>