Re: [Boost-bugs] [Boost C++ Libraries] #8933: on the windows platform async reads with multiple threads can produce random EOF errors

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8933: on the windows platform async reads with multiple threads can produce random EOF errors
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-08-11 01:33:07

#8933: on the windows platform async reads with multiple threads can produce
random EOF errors
-----------------------------------------+----------------------------
  Reporter:  Shane Powell <killerbee@…>  |      Owner:  chris_kohlhoff
      Type:  Bugs                        |     Status:  new
 Milestone:  To Be Determined            |  Component:  asio
   Version:  Boost 1.54.0                |   Severity:  Showstopper
Resolution:                              |   Keywords:
-----------------------------------------+----------------------------

Comment (by smueller@…):

 I think that this is right, but for the wrong reason. I also don't like
 the idea of re-posting to the IOcompletionport when we can execute the
 callback in-place.

 The comment about the document, however, is irrelevant, as it refers to
 the mode of WSASend/Recv/etc which uses the OVERLAPPED struct and a
 callback function. In this mode, the callback is executed as an APC which
 requires that the thread be placed in an alertable state. It is well-
 agreed upon that this does not make for a maintainable program. They
 aren't talking about iocompletionport, for which all you have to do is
 have your handle assigned to the iocompletionport for it to queue
 completion messages on threads calling GetQueuedCompletionStatus.

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