-
Key: DDS15-171
-
Legacy Issue Number: 10369
-
Status: open
-
Source: Honeywell ( James Richardson)
-
Summary:
Context: "If the kind is set to KEEP_ALL, then the Service will attempt to maintain and deliver all the values of the instance to existing subscribers. The resources that the Service can use to keep this history are limited by the settings of the RESOURCE_LIMITS QoS. If the limit is reached, then the behavior of the Service will depend on the RELIABILITY QoS. If the reliability kind is BEST_EFFORT, then the old values will be discarded." This violates the ordinary English meaning of KEEP_ALL. Can't the same effect be achieved by specifying KEEP_LAST with history_depth=max_samples_per_instance? If so, then KEEP_ALL should not be allowed for RELIABILITY=BEST_EFFORT.
-
Reported: DDS 1.2 — Fri, 22 Sep 2006 04:00 GMT
-
Updated: Tue, 15 Mar 2016 14:41 GMT
DDS15 — Force KEEP_ALL to be RELIABLE Section: 2.1.3.18
- Key: DDS15-171
- OMG Task Force: Data Distribution Service 1.5 RTF