network tables ordering?

[truher]

quick question for Peter:

if i have a single networktables publisher, is the order of publish events preserved in (remote) subscriber readQueue results?

so, for example, the publisher writes odometry at regular intervals: it would be nice if those odometry updates were received in sender-sorted order in readQueue (which would be time-sorted order for this sender)

?

[PeterJohnson]

Yes, order in this scenario should be preserved in the current C++ implementation, although it is not guaranteed by the spec. Note the spec only talks about the protocol; readQueue is an API feature. It's also worth noting that depending on pub/sub options (e.g. send duplicates, send all) you may or may not receive all the updates that were sent, but they should be in order.