DDS 1.0 NO IDEA Avatar
  1. OMG Issue

DDS — DDS ISSUE# 17] Clarify consequence of changing partitions

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

    Ref-17 PartitionQos_behavior_on_change

    The specification does not make it clear whether changing the
    PARTITION QoS on a Publisher or Subscriber affects the existing
    DataReader or DataWriter establishing some "associations" that did not
    exist before, or breaking associations that existed.

    Furthermore the specification does not describe whether the
    INCOMPATIBLE_QOS listeners/ status will be triggered

    Given that partitions are intended to be used to separate logically
    separate 'communication words' so that you can isolate things it would
    seem that changing partitions should affect existing DataReader and
    writers and not trigger the INCOMPATIBLE_QOS.

    **PROPOSAL**

    Modify section 2.1.3.9 to clarify that (1) changing the PARTITION QoS
    on a Publisher or Subscriber does affect the existing DataReader or
    DataWriter entities. It may establish new "associations" that did not
    exist before, or break existing associations.

    Also explain in section 2.1.3.9 that not matching the PARTITION QoS
    does not trigger the INCOMPATIBLE_QOS listener nor change the
    associated status.

  • Reported: DDS 1.0b1 — Tue, 23 Dec 2003 05:00 GMT
  • Disposition: Resolved — DDS 1.0
  • Disposition Summary:

    see below

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