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-13 11:41:58
#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 anonymous):
* status: reopened => closed
* resolution: => wontfix
Comment:
I suspect you misinterpreted my response. To clarify:
- I did not suggest there are no use cases for a timed read in a
synchronous context.
- I did say there are use cases for synchronous reads and writes, and so I
will not consider removing them (as the trac item suggests).
- My reference to POSIX is that it also provides *non-timed* synchronous
operations, such as read() and write(). They are the equivalent of asio's
synchronous functions. They are used in similar circumstances.
If you need cancellability, then my answer will always be that you should
use asynchronous operations. I am interested in improving techniques to
make it easier to use asynchronous operations in synchronous call
contexts. But as this trac item is predicated on changing the behaviour of
the synchronous functions, I'm closing it.
P.S. your select()-based code is broken :)
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/2832#comment:5> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:02 UTC