On 28/07/2020 15:04, Michael McMahon wrote:
The code is technically racy on the GET test, but it's often the case when you want something to be racy then it turns out not to be in practice, 99 times out of a 100 anyway (figures made up). I was thinking you could put a random sleep on the client side before calling cancel (say between 1ms and the SERVER_LATENCY constant). Print out the random value tooin case it finds a problem.
Oh - that's a good point. Let me try that. best regards, -- daniel
