rticommunity / rticonnextdds-connector

RTI Connector for Connext DDS is a lightweight technology that enables DDS data to be accessed with Javascript (Node.js), Python, and Lua.
Other
56 stars 33 forks source link

Setting ownership qos #65

Closed VectorUrsRudolph closed 5 years ago

VectorUrsRudolph commented 5 years ago

Hi, I try to connect to my topic with exclusive ownership, but the connector shows alway up with shared ownership.

The xml section is: `

VOLATILE_DURABILITY_QOS RELIABLE_RELIABILITY_QOS 10 0 EXCLUSIVE_OWNERSHIP_QOS ` Any ideas?
samuelraeburn commented 5 years ago

Hi,

I believe the issue is that you are using topic_qos tags to configure your QoS. Internally Connector is based on top of XML Application Creation which doesn't expose any way of doing this out of the box. It might be possible to achieve what you are trying to do with , but the easiest option would be for you to place your QoS in and tags:

<datawriter_qos>
    <durability>
        <kind>VOLATILE_DURABILITY</kind>
    </durability>
    <reliability>
        <kind>RELIABLE_RELIABILITY_QOS</kind>
        <max_blocking_time>
            <sec>10</sec>
            <nanosec>0</nanosec>
        </max_blocking_time>
    </reliability>
    <ownership>
        <kind>EXCLUSIVE_OWNERSHIP_QOS</kind>
    </ownership>
</datawriter_qos>
<datareader_qos>
    <durability>
        <kind>VOLATILE_DURABILITY</kind>
    </durability>
    <reliability>
        <kind>RELIABLE_RELIABILITY_QOS</kind>
        <max_blocking_time>
            <sec>10</sec>
            <nanosec>0</nanosec>
        </max_blocking_time>
    </reliability>
    <ownership>
        <kind>EXCLUSIVE_OWNERSHIP_QOS</kind>
    </ownership>
</datareader_qos>

I tested this using the shipped Connector example and the ownership QoS policy was correctly applied.

Is this a possibility for your use-case? Sam

VectorUrsRudolph commented 5 years ago

This works for me, thanks! I think I tried this before but for somehow reasons it don't worked.