Re: [Boost-bugs] [Boost C++ Libraries] #4167: RFC: asio::io_service::async_stop() to handle signals

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4167: RFC: asio::io_service::async_stop() to handle signals
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2010-05-01 22:41:59

#4167: RFC: asio::io_service::async_stop() to handle signals
------------------------------------+---------------------------------------
  Reporter:  giecrilj@…             |       Owner:  chris_kohlhoff    
      Type:  Feature Requests       |      Status:  closed            
 Milestone:  Boost 1.43.0           |   Component:  asio              
   Version:  Boost 1.42.0           |    Severity:  Problem           
Resolution:  wontfix                |    Keywords:  signal, event loop
------------------------------------+---------------------------------------
Changes (by chris_kohlhoff):

  * status:  new => closed
  * type:  Bugs => Feature Requests
  * resolution:  => wontfix

Comment:

 Thanks for the suggestion, but I do not consider this the right approach
 for handling signals. The "correct" way would be to handle signals just
 like other asynchronous events. I will probably add this support at some
 point.

 In the meantime, you could use a pipe (as you said), but you can also
 process the signals synchronously using sigwait(). All of the HTTP server
 examples take this approach.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/4167#comment:1>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.