Publisher is forced to use DSM SequenceNumber
This is currently a limitation:
The DataSetMessageSequenceNumber
is forced to 1, whereas the publisher may want to ignore this field. This can be a problem of non-resynchronizeable Pub/Sub (See also #1180 (closed)).
Probably, after #1180 (closed) is solved this lock will fall, however, it remains that we do not want to force Publisher options.
Example: Pub sends SeqNum=1..1000, and Sub receives them. Pub reboots and restart sending from 1. All messages until 1000 will be ignored.
Edited by Jérémie Chabod