Skip to content
Open
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
9 changes: 7 additions & 2 deletions docs/fastdds/discovery/discovery_server.rst
Original file line number Diff line number Diff line change
Expand Up @@ -65,22 +65,27 @@ In this architecture there are several key concepts to understand:
* It is important to note that the discovery times will be negatively affected when using this type of *server*,
since periodically writing to a file is an expensive operation.

- A |CLIENT| is a participant that connects to one or more *servers* from which it receives only the discovery
- A |CLIENT| |Pro| is a participant that connects to one or more *servers* from which it receives only the discovery
information they require to establish communication with matching endpoints.

* *Clients* require prior knowledge of the *servers* to which they want to link.
Basically, it consists of a list of locators where the *servers* are listening, namely, an IP address and a port.
These locators also define the transport protocol (UDP or TCP) the client will use to contact the *server*.
* **Efficient Discovery Filterning** |Pro| : The optimized topic matching algorithm that enables *clients* to
receive only relevant discovery information is available exclusively in *Fast DDS Pro*. In the open-source
Fast DDS distribution, *clients* operate with the same discovery behavior as *super clients*, receiving all
discovery information from the server.

- A |SUPER_CLIENT| is a *client* that receives the discovery information known by the *server*, in opposition to
*clients*, which only receive the information they need.
Pro *clients*, which only receive the information they need.

.. note::

A |SUPER_CLIENT| does not behave as a *Server* as it only receives the discovery information through the *Server* to
which it is connected.
It will not connect to other servers, and it will not redistribute the information it receives.
Any DomainParticipant discovered by the *Server* with no endpoints will not be known by the |SUPER_CLIENT|.
In the open-source Fast DDS distribution, all *clients* function as *super clients* by default.

- *Servers* do not require any prior knowledge of their *clients*, but they must listen in the address specified
by the locator provided to the *clients*.
Expand Down
2 changes: 1 addition & 1 deletion docs/fastdds/discovery/general_disc_settings.rst
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ The possible values are:
| Discovery Server | |SERVER| | The DomainParticipant acts as a hub for discovery traffic, receiving |
| | | and distributing discovery information. |
| +---------------------+--------------------------------------------------------------------------+
| | |CLIENT| | The DomainParticipant acts as a client for discovery traffic. |
| | |CLIENT| |Pro| | The DomainParticipant acts as a client for discovery traffic. |
| | | It sends its discovery information to the server, and it receives |
| | | only the information that is relevant to it. |
| +---------------------+--------------------------------------------------------------------------+
Expand Down
8 changes: 6 additions & 2 deletions docs/fastdds/faq/discovery/discovery.rst
Original file line number Diff line number Diff line change
Expand Up @@ -74,14 +74,18 @@ Discovery Frequently Asked Questions

.. collapse:: What is a client in this context?

|br| A ``CLIENT`` is a participant that connects to one or more servers from which it receives only the discovery information they require to establish communication with matching endpoints.
|br| A ``CLIENT`` is a participant that connects to one or more servers from which it receives discovery information to establish communication with matching endpoints.
With Fast DDS Pro, clients benefit from an optimized matching algorithm that filters discovery data, delivering only the information necessary for communication with relevant endpoints.
In the open-source Fast DDS distribution, clients operate with the same discovery behavior as super clients, receiving all discovery information from the server.
For further information, refer to :ref:`discovery_server`.

----------

.. collapse:: What is the difference between a CLIENT and a SUPER_CLIENT?

|br| A ``SUPER_CLIENT`` is a client that receives the discovery information known by the server, in opposition to clients, which only receive the information they need.
|br| A ``SUPER_CLIENT`` is a client that receives all discovery information known by the server.
In Fast DDS Pro, standard clients receive only filtered, relevant discovery information through an optimized matching algorithm, improving efficiency and reducing network overhead.
In the open-source Fast DDS distribution, all clients operate as super clients by default.
For further information, refer to :ref:`discovery_server`.

----------
Expand Down