Issues for Data Distribution Service 1.4 Revision Task Force

To comment on any of these issues, send email to [email protected]. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to [email protected].

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 10088: section 2.1.2.5.2.16 "get_default_datareader_qos" Jira Issue DDS11-13
Issue 12529: 'synchrobnous' and 'asynchronous' switched Jira Issue DDS11-14
Issue 15430: DDS should use typed modules Jira Issue DDS11-15

Issue 10088: section 2.1.2.5.2.16 "get_default_datareader_qos" (data-distribution-rtf)

Click here for this issue's archive.
Source: Vanderbilt University (Mr. Joe Hoffert, nobody)
Nature: Uncategorized Issue
Severity:
Summary:
I just wanted to let someone know about a typographical error I saw in the DDS spec 05-12-04-1. In section 2.1.2.5.2.16 "get_default_datareader_qos" The second paragraph reads in part      "The values retrieved get_default_datareader_qos will match the set of values specified  on the last successful call to get_default_datareader_qos, ..."        I believe that last function should be "set_default_datareader_qos" rather than "get_default_datareader_qos". This is consistent with other sections of the specification and makes sense. I just wanted to point this out. It looks like there used to be this same kind of error for set_default_datawriter_qos but was fixed in 05-12-04-1. I didn't see this listed in the DDS issues.    

Resolution:
Revised Text:
Actions taken:
August 8, 2006: received issue

Issue 12529: 'synchrobnous' and 'asynchronous' switched (data-distribution-rtf)

Click
here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:
While reading the DDS specification, 'Data Distribution Service for Real-time Systems Version 1.2 OMG Available Specification formal/07-01-01', I found that the 'synchrobnous' and 'asynchronous' was switched as highlighted in red in the below paragraph in the spec.      <para #4, page 11>  On the subscriber’s side however, there are more choices: relevant information may arrive when the application is busy doing something else or when the application is just waiting for that information. Therefore, depending on the way the application is designed, asynchronous notifications or synchronous access may be more appropriate. Both interaction modes are allowed, a Listener is used to provide a callback for synchronous access and a WaitSet associated with one or several Condition objects provides asynchronous data access

Resolution:
Revised Text:
Actions taken:
May 14, 2008: received issue

Issue 15430: DDS should use typed modules (data-distribution-rtf)

Click
here for this issue's archive.
Source: Remedy IT (Mr. Johnny Willemsen, jwillemsen(at)remedy.nl)
Nature: Revision
Severity: Significant
Summary:
The DDS specfication has typed interfaces (writer/reader/etc) which are currently not expressed in IDL. The DDS specification should use the typed modules as introduced in the dds4ccm specification to express all interfaces explicitly in IDL, including the typed ones.

Resolution:
Revised Text:
Actions taken:
August 23, 2010: received issue