Implement dataSetMessage sequence number mechanism
Publisher side:
- to simplify configuration this options will be automatically set
Subscriber side:
- Subscriber scheduler automatically check dataSetMessages sequence number if tuple [PublisherId, DataSetWriterId] has been configured to filter dataSetMessage
- If a gap in sequence number is catch by subscriber an applicative callback is called user configurable
Edited by Gael Raphal