Grabbing ntpClientRecvTime Twice

[victorstewart]

In udpSocket: didReceiveData: fromAddress: withFilterContext: you grab the ntpClientRecvTime, then you call decodePacket: and grab it again right after?

I assume the 2nd one should be skipped, plus it'll be about 8 nanoseconds later.

[gavineadie]

It would seem the second assignment is unnecessary (though 8 nanoseconds don't amount to a hill of beans in this code) !! I'll fix it next time I make any changes, or sooner if that seems a long way off.

…

On Aug 3, 2017, at 3:53 PM, Victor Stewart ***@***.***> wrote: In udpSocket: didReceiveData: fromAddress: withFilterContext: you grab the ntpClientRecvTime, then you call decodePacket: and grab it again right after? I assume the 2nd one should be skipped, plus it'll be about 8 nanoseconds late. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.