From: JH (jupiter.hce_at_[hidden])
Date: 2019-08-27 06:34:51
On 8/27/19, Gavin Lambert via Boost <boost_at_[hidden]> wrote:
> On 27/08/2019 02:05, JH wrote:
>> Nope, a function wrapped the pair of expires_at and async_wait for
>> absolute time or expires_from_now async_wait for relative time.
> Well, the underlying expiration mechanism is the same for both -- in
> fact expires_from_now is implemented by calling expires_at internally.
> Are you sure you're calculating the correct ptime for expires_at?
> It may perhaps help to use expires_from_now(x) to set an expiration and
> then call expires_at() to read the absolute expiration time that this
> set, and compare it with what you had calculated.
> Or conversely to call expires_at(x) and then read the relative time with
> expires_from_now() to see if that is as expected.
The expires_at(x) works at the first call, to workaround, I did
exactly as you suggested to do the rest of calls using
expires_from_now() for the time being, I do want to know why the
second call of expires_at had that kind of problem, will do further
Thank you very much.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk