3 ms·
Specifying a deadline timestamp instead of a countdown could run into problems if a given machine has an improperly configured clock. I think the risk of any m
by dbmikus 10y ago
Specifying a deadline timestamp instead of a countdown could run into problems if a given machine has an improperly configured clock.
I think the risk of any machine having an incorrect timestamp is greater than a library implementer not recalculating the countdown correctly. Whenever possible, I prefer to stay away from timestamps. They're a fickle thing.
- slrz 10y agoWhy would it matter? The deadline would be specified in terms of a monotonic clock that's unaffected by wall time adjustments. So even if some crude NTP implementation steps your clock by seconds (or a leap second is inserted), it shouldn't matter for the deadline calculation.
- Bino 10y agoI think most of my timeout/deadlines relative to the monotonic time. Hence specifying the absolute monotonic time would just involve yet another syscall (to query the time). Is there a really good argument to specify a absolute monotonic time?
- dbmikus 10y agoThen you need to send information to agree on a monotonic clock time.