Legacy Issue Number: 16532
Source: ZettaScale Technology ( Angelo Corsaro)
Some of the DDS QoS Policies are Request vs. Offered in the sense that
the value of matching policies on communicating entities have to satisfy a
specific ordering relationship. Specifically, the policy set on the receiving side
should always be less or equal than the analogous QoS Policy on the
sending side. As a result there is a natural total ordering for RxO Policies
which is not currently captured nor reflected in the API.
As a consequence also QoS should be defining a total order.
Ensure that all RxO Policies implement the Comparable interface. This is
pretty logical as for this QoS Policies it has to be established
a total order.
Let QoS classes also implement a comparable interface.
Reported: DDS-Java 1.0b1 — Wed, 7 Sep 2011 04:00 GMT
Disposition: Resolved — DDS-Java 1.0b2
Define an interface RequestedOffered; all QoS policy types that require requested/offered compatibility extend this interface. The interface has one method, requestedOfferedContract, which returns a Comparable object. That objects compares the policy against another instance of the policy based on the requested/offered compatibility rule(s) for that policy type.
Updated: Fri, 6 Mar 2015 20:58 GMT
DDSJAVA — RxO QoS Policies should be Comparable (idem for QoS)
- Key: DDSJAVA-23
- OMG Task Force: Java 5 Language PSM for DDS 1.0 FTF