DDS 1.1 RTF Avatar
  1. OMG Issue

DDS11 — (R#115b) Incorrect description of QoS for built-in readers

  • Key: DDS11-111
  • Legacy Issue Number: 8569
  • Status: closed  
  • Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
  • Summary:

    Summary:

    In Section 2.1.5, there is a table that lists all the QoS policies that are used to create built-in readers. Since the policies are for creating built-in readers, the table should only list the QoS for the corresponding subscriber, reader, and topic. It shouldn't list any policies that occur only in DataWriterQos. Specifically, TRANSPORT_PRIORITY, LIFESPAN, and OWNERSHIP_STRENGTH, all of which apply only to DataWriters, are currently listed erroneously.
    The following QoS are supposed to apply to DataReaders (or their related entities) but are missing from the table: ReaderDataLifecycleQosPolicy, EntityFactoryQosPolicy

    For the QoS that are already listed in the table, some of them don't list the default values of some of the fields.

    DURABILITY: missing service_cleanup_delay value
    RELIABILITY: missing max_blocking_time value

    Proposed Resolution:

    Remove TRANSPORT_PRIORITY, LIFESPAN, and OWNERSHIP_STRENGTH from the table.

    Add the following values:

    READER_DATA_LIFECYCLE autopurge_nowriter_samples_delay = INFINITE
    ENTITY_FACTOR autoenable_created_entities = TRUE
    DURABILITY service_cleanup_delay = 0
    RELIABILITY max_blocking_time = 100 milliseconds

    Proposed Revised Text:
    Change the table in section 2.1.5, page 2-129, as described above.

  • Reported: DDS 1.0 — Mon, 14 Mar 2005 05:00 GMT
  • Disposition: Resolved — DDS 1.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT