Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3504: deadline_timer (based on UTC time) is not suitable for communication timeouts
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-11-02 22:12:11
#3504: deadline_timer (based on UTC time) is not suitable for communication
timeouts
--------------------------------------------+-------------------------------
Reporter: Bjarne Laursen <bla@â¦> | Owner: chris_kohlhoff
Type: Feature Requests | Status: closed
Milestone: Boost 1.41.0 | Component: asio
Version: Boost 1.41.0 | Severity: Problem
Resolution: wontfix | Keywords:
--------------------------------------------+-------------------------------
Comment (by Aaron_Wright@â¦):
Replying to [comment:10 kjohnson@â¦]:
> I may be wrong, but I think the attached file "monotone_timer.hpp-
NO_MUTEX" suffers from really bad roll over issues. Multiplying a rolling
monotonic timer by a constant (1000000000/frequency.QuadPart on line 80)
doesn't produce a valid monotonic nanosecond count.
I'm investigating an issue I've had where timers have stopped firing. I
used an implementation just like "monotone_timer.hpp-NO_MUTEX", and I was
wanting to narrow down the cause of my problem.
Would it be possible to get a little more detail about why that equation
doesn't "produce a valid monotonic nanosecond count"? I would really
appreciate it.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/3504#comment:15> 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:07 UTC