-
Key: DDSIRTP26-31
-
Status: open
-
Source: Georgia Institute of Technology ( Seulbae Kim)
-
Summary:
In the wire representation figures of 9.4.5.4 and 9.4.5.5, `SequenceNumber writerSN` is shown as:
+---------------+---------------+---------------+---------------+ + SequenceNumber writerSN + +---------------+---------------+---------------+---------------+
as if it only occupies 4 bytes.
In all other places (9.4.2.6, 9.4.5.6, 9.4.5.7, 9.4.5.8, 9.4.5.14, and 9.6.4.7), SequenceNumbers are represented explicitly as 64-bit values:
+---------------+---------------+---------------+---------------+ | | + SequenceNumber gapStart + | | +---------------+---------------+---------------+---------------+
In hindsight, the plus signs does indicate that the field is larger than it looks, but unless there is a clear reason, can those representations be unified to remove potential confusion and provide better readability?
-
Reported: DDSI-RTPS 2.5 — Tue, 23 Aug 2022 15:31 GMT
-
Updated: Wed, 24 Aug 2022 17:03 GMT
DDSIRTP26 — Inconsistency in the wire representation of SequenceNumber type fields
- Key: DDSIRTP26-31
- OMG Task Force: DDSI-RTPS 2.6 RTF