-
Key: DDS15-187
-
Legacy Issue Number: 19649
-
Status: open
-
Source: ZettaScale Technology ( Angelo Corsaro, PhD.)
-
Summary:
The third paragraph of the DURABILITY section (2.1.3.4) describes the semantics that has to be provided by a durability service for TRANSIENT and PERSISTENT topics. Specifically, it states that given a Topic T with DURABILITY QoS set to TRANSIENT or PERSISTENT then the "built-in fictitious" DataReader and DataWriter used by the Durability Service to receive/distribute data have to be created with the same QoS T. Yet, nothing is said with respect to the role of the PARTITION QoS. Section 2.1.3.13 clearly states that:
"For a DataReader to see the changes made to an instance by a DataWriter, not only the Topic must match, but also they must share a common partition."
Thus based on the current specification the Durability Service DataReader and DataWriter would only match the applications DataReader and DataWriter that are in the default partition.
-
Reported: DDS 1.4 — Wed, 29 Oct 2014 04:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
DDS15 — Durability Implementation Description does not consider the role of partitions
- Key: DDS15-187
- OMG Task Force: Data Distribution Service 1.5 RTF