-
Key: DDS11-69
-
Legacy Issue Number: 8424
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
There are two limitations to the PublicationMatchStatus and SubscriptionMatchStatus that prevent them from being used to detect the loss of a match:
· The specification does not indicate whether those statuses are considered to have changed when a match is lost (e.g. as a result of a loss of liveliness or an incompatible QoS change).
· The status structures contain fields that indicate the total number of matches that have ever occurred, but they lack fields to indicate the number of current matches.Proposed Resolution:
Two fields should be added to each status structure: current_count and current_count_change. The specification should be updated to state that the publication and subscription match statuses are considered to have changed both when a match is established and when it is lost.Proposed Revised Text:
Update the table in 2.1.4.1 as follows:DataReader SUBSCRIPTION_MATCH_STATUS The DataReader has found a DataWriter that matches the Topic and has compatible QoS or has stopped communicating with a DataWriter that was previously considered to have matched.
DataWriter PUBLICATION_MATCH_STATUS The DataWriter has found DataReader that matches the Topic and has compatible QoS or has stopped communicating with a DataReader that was previously considered to have matched.
Update PublicationMatchStatus and SubscriptionMatchStatus in figure 2-13 to add the following attributes to each:
current_count : long
current_count_change : longUpdate the PublicationMatchStatus section of the table on page 2-119 with the following rows:
current_count The number of DataReaders currently matched to the concerned DataWriter.
current_count_change The change in current_count since the last time the listener was called or the status was read.Update the SubscriptionMatchStatus section of the table on page 2-119 with the following rows:
current_count The number of DataWriters currently matched to the concerned DataReader.
current_count_change The change in current_count since the last time the listener was called or the status was read.Modify the declarations of the PublicationMatchStatus and SubscriptionMatchStatus structures in the IDL PSM in 2.2.3 as follows:
struct PublicationMatchStatus
{ long total_count; long total_count_change; long current_count; long current_count_change; InstanceHandle_t last_subscription_handle; };
struct SubscriptionMatchStatus
{ long total_count; long total_count_change; long current_count; long current_count_change; InstanceHandle_t last_publication_handle; };
-
Reported: DDS 1.0 — Tue, 1 Mar 2005 05:00 GMT
-
Disposition: Resolved — DDS 1.1
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS11 — (R#135) Add fields to PublicationMatchStatus and SubscriptionMatchStatus
- Key: DDS11-69
- OMG Task Force: Data Distribution Service RTF