Re: [Boost-bugs] [Boost C++ Libraries] #2832: Asio sync IO functions need timeout parameters

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2832: Asio sync IO functions need timeout parameters
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2010-01-12 22:12:11

#2832: Asio sync IO functions need timeout parameters
-----------------------------------------------------+----------------------
  Reporter:  Stephan Menzel <stephan.menzel@…>       |       Owner:  chris_kohlhoff
      Type:  Bugs                                    |      Status:  closed        
 Milestone:  Boost 1.39.0                            |   Component:  asio          
   Version:  Boost 1.38.0                            |    Severity:  Problem       
Resolution:  wontfix                                 |    Keywords:                
-----------------------------------------------------+----------------------
Changes (by chris_kohlhoff):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 Just because you can't imagine a use case doesn't mean there aren't any :)

 I don't agree with either of the suggestions:

 1) '''Remove the synchronous functions.''' They may be useful to
 applications that are signal aware, that use non-blocking i/o, or just
 plain don't care. They're in POSIX this way so they're staying in asio
 this way.

 2) '''Add timeout parameters.''' It's the wrong place in the API to add a
 timeout as it does not scale to higher levels of abstraction i.e. composed
 operations. Timers are kept separate so that they may be equally used with
 composed operations such as async_read or async_read_until as with the
 socket's async_read_some operation.

 I'm interested in exploring and improving these use cases, but in my
 opinion these are not viable solutions.

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