Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[20709] Remove RTPSMessageGroup from aliases-api includes #744

Merged
merged 1 commit into from
May 24, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion docs/03-exports/aliases-api.include
Original file line number Diff line number Diff line change
Expand Up @@ -1032,7 +1032,6 @@

.. |MonitorServiceDataReaderQos-api| replace:: :cpp:class:`MonitorServiceDataReaderQos <eprosima::fastdds::statistics::dds::MonitorServiceDataReaderQos>`

.. |RTPSMessageGroup| replace:: :cpp:class:`RTPSMessageGroup <eprosima::fastrtps::rtps::RTPSMessageGroup>`
.. |MessageReceiver| replace:: :cpp:class:`MessageReceiver <eprosima::fastrtps::rtps::MessageReceiver>`

.. |WriteParams-api| replace:: :cpp:class:`WriteParams <eprosima::fastrtps::rtps::WriteParams>`
Expand Down
4 changes: 2 additions & 2 deletions docs/fastdds/statistics/dds_layer/topic_names.rst
Original file line number Diff line number Diff line change
Expand Up @@ -66,8 +66,8 @@ the corresponding user's callback.
The ``_fastdds_statistics_network_latency`` statistics topic collects data related with the network latency (expressed
in *ns*) between any two communicating locators.
This measurement provides information about the transport layer latency.
The measured latency corresponds to the time spent between the message being written in the |RTPSMessageGroup| until the
message being received in the |MessageReceiver|.
The measured latency corresponds to the time spent between the message being written until the message being received
in the |MessageReceiver|.

.. important::
In the case of :ref:`transport_tcp_tcp`, the reported latency also includes the time spent on the datagram's CRC
Expand Down