Age | Commit message (Collapse) | Author |
|
|
|
Otherwise we can imagine that two clients changing this value at the same
time would mix things up.
ref #3275
|
|
|
|
fix #3275
|
|
|
|
This reverts commit 3f088e7b3a1467a88e7c5ff9fb60dc4609d2bfa3.
|
|
This reverts commit ba879a882e031d7b8503f78fe41d1210000c96ca.
|
|
This reverts commit d62ca9f87906be6f046fe9d07afb8bfb69c166e3.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ref #3273
|
|
ref #3273
|
|
fix #3273
|
|
|
|
fix #3339
|
|
|
|
|
|
|
|
fix #3337
Because apparently the IDs are not always incrementing. We still use them to
know the order of two messages that were received at the same second (in
this case, the ID will always be incrementing).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|