News for hackers. Stuff that matters.

A comment on Building a concurrent TCP server with libmill. Parent comment

Re:Building a concurrent TCP server with libmill by obstinate on Saturday July 25, 2015 @02:13PM (#9948431)
Yes, and if you set the deadline on the client, the server knows (subject to its time skew) when the request needs to finish. With a timeout, you have to factor in latency, which is necessarily error prone.

Basically, deadline is a context-free timeout.

[ Parent | on HN ]
Re:Building a concurrent TCP server with libmill by huhtenberg on Saturday July 25, 2015 @05:54PM (#9949174)
... unless, of course, it's on the wall clock scale, in which case changing machine time will invalidate all your deadlines. Just need to be careful to use something like 'ticks from the last boot' rather than UTC time.
[ Parent | on HN ]
Re:Building a concurrent TCP server with libmill by obstinate on Saturday July 25, 2015 @07:05PM (#9949383)
In competently run environments, wall clock changes are smeared. :) there is no way to use ticks since last boot, since the server will have a different value from the client.
[ Parent | on HN ]