Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2832: Asio sync IO functions need timeout parameters
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-03-09 11:35:30
#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: Showstopper
Resolution: wontfix | Keywords:
-----------------------------------------------------+----------------------
Comment (by anonymous):
This is probably the dumbest ticket discussion I ever read. [[BR]]
Everybody who is using blocking socket functions wants a timeout for them.
But no, there is a better solution, the "official" one: simulate a
blocking function by using asynchronous functions and waiting for them to
finish.[[BR]]
Wow. Talk about scratching your left ear with your right foot. I don't
know about you guys, but Computer Science 101 taught me that when
encountering a problem a program should stop and handle it, not wait and
wait and wait some more for it to solve itself.[[BR]]
Connect or read functions which take minutes to return are just plain
stupid. They should timeout and do it fast, not wait or retry
forever.[[BR]]
PS: If you like the asynchronous approach so much, why don't you create
some overloads for the synchronous functions which do what
[http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/example/timeouts/blocking_tcp_client.cpp
this] tries to explain.
PPS: Synchronous and asynchronous are very very different. Stop suggesting
asynchronous solutions for synchronous problems or designs.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/2832#comment:18> 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:12 UTC