Request for code & logic review

Daniel Franke dfoxfranke at gmail.com
Fri Nov 25 01:57:38 UTC 2016


On 11/24/16, Eric S. Raymond <esr at thyrsus.com> wrote:
> Daniel Franke <dfoxfranke at gmail.com>:
>> t_1, the origin timestamp, is the time according to the client at
>> which the request was sent.
>> t_2, the transmit timestamp, is the time according to the server at
>> which the request was received.
>> t_3, the receive timestamp, is the time according to the server at
>> which the reply was sent.
>> t_4, the destination timestamp, is the time according to the client at
>> which the reply was received.
>
> Er...
>
>> t_2, the transmit timestamp, is the time according to the server at
>> which the request was received.
>
> The "transmit timestamp" is a receipt time?  Are you sure that's right

It should be,

t_1, the origin timestamp, is the time according to the client at
which the request was sent.
t_2, the receive timestamp, is the time according to the server at
which the request was received.
t_3, the transmit timestamp, is the time according to the server at
which the reply was sent.
t_4, the destination timestamp, is the time according to the client at
which the reply was received.

The reference timestamp isn't really used for anything, and the
destination timestamp obviously can't be part of the packet.


More information about the devel mailing list