You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -898,7 +898,7 @@ in [ros2_qos_profiles.xml](rmw_connextdds/resource/xml/ros2_qos_profiles.xml),
898
898
for example, `ros2::rmw_connextdds.base_participant`. See [Built-in ROS 2 QoS Profiles](#built-in-ros-2-qos-profiles) for more information about these QoS profiles
899
899
and how to use them.
900
900
901
-
### Customize Endpoint QoS
901
+
### Customize DataWriter and DataReader QoS
902
902
903
903
`rmw_connextdds` will include the topic name when querying for the default QoS values
904
904
used by a new DDS endpoint. This allows users to take advantage of [topic filters](https://community.rti.com/static/documentation/connext-dds/6.0.1/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/Topic_Filters.htm)
@@ -1454,7 +1454,7 @@ Upon creation of a [DataWriter](#datawriter-creation) or [DataReader](#datareade
1454
1454
are able to let Connext manipulate ROS 2 messages without any additional data
1455
1455
representation conversion (as was for exaple the case with the previous
1456
1456
implementation, `rmw_connext_cpp`).
1457
-
- Determine the mangled version of the topic name (see [Customize Endpoint QoS](#customize-endpoint-qos)
1457
+
- Determine the mangled version of the topic name (see [Customize DataWriter and DataReader QoS](#customize-datawriter-and-datareader-qos)
1458
1458
for a summary of the name mangling rules).
1459
1459
- Check if a Topic with the specific name and data type has already been created
1460
1460
by calling [`DDS_DomainParticipant_find_topic()`](https://community.rti.com/static/documentation/connext-dds/6.0.1/doc/api/connext_dds/api_c/group__DDSDomainParticipantModule.html#ga5d03738356707f3375ffddc7d1669161).
0 commit comments