Skip to content

Late Joining for Keyed Topics - Propagate History QoS from DDS (e.g. KEEP_LAST_HISTORY_QOS: 1) #526

@seichmann

Description

@seichmann

Describe the feature

DDS supports late joining for DataReaders, which supports use cases for keyed topics that a reader can get messages after they were produced (e.g. when the Zenoh Router joins the network in operation after the initial setup on the fly):

DDS Configs:

			<history>
				<kind>KEEP_LAST_HISTORY_QOS</kind>
				<depth>1</depth>
			</history>

Advanced Subscriber/Publisher of Zenoh Core might be usable to emulate that QoS behavior derived from the DDS history QOS definition.

Concrete Use Case:

DDS object are keyed by a UUID. For each UUID, a last position is propagated. It should be possible for any client application to get the last position of all DDS object when the initialy connect to the DDS domain behind the Zenoh Router.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions