Menu ▾ ▴

#50 Server messages should use 64-bit timestamps

Future
open
nobody
None
8
2013-10-11
2013-10-11
Bruce Merry
No

Although this won't actually matter until long after I'm dead, the uint32_t _time field should be upgraded to 64-bit. Note that it should not be time_t, since the size of that is machine dependent and this is part of a wire protocol.

There are quite a few messages that are affected, plus the message header, and no doubt some of the bookkeeping in udpmessenger.

Discussion

  • Bruce Merry

    Bruce Merry - 2013-10-11
    • summary: MarkMessage should use 64-bit timestamps --> MarkMessage and SubmitMessage should use 64-bit timestamps
     

  • Bruce Merry

    Bruce Merry - 2013-10-11
    • summary: MarkMessage and SubmitMessage should use 64-bit timestamps --> Server messages should use 64-bit timestamps
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1 +1,3 @@
 Although this won't actually matter until long after I'm dead, the `uint32_t _time` field should be upgraded to 64-bit. Note that it should *not* be time_t, since the size of that is machine dependent and this is part of a wire protocol.
+
+There are quite a few messages that are affected, plus the message header, and no doubt some of the bookkeeping in udpmessenger.
     

Log in to post a comment.

MongoDB Logo MongoDB