On Sat, 2017-12-09 at 22:58 +0200, Johan Hedberg wrote:
On Sat, Dec 09, 2017, Steve Brown wrote:
These are publish retransmits. However, the transaction ID's in theIf I understand right, then the transaction id is a model-layer
received messages are all the same. It's the "trans_id" field in
log in my earlier post.
so you'd need to take care of correct handling of duplicates in your
An upper layer, like my server, getting multiple messages with theAre you mixing transaction id (a model layer feature) and sequence
sequence number isn't what I'd expect. What am I missing?
number (network/transport layer feature)? I didn't see any indication
that your handlers would be getting the same squence number multiple
times, rather they're getting the same transaction id multiple times.
Sequence number duplicates should get filtered out latest by the
transport layer's replay protection (if the network message cache
catch them before that).
Yes, I've conflated sequence number and transaction id.
It's clear now.
Thanks for the clarification,