Clarify super client discovery information (#555)

* Refs #19432: clarify super client discovery information Signed-off-by: JLBuenoLopez-eProsima <[email protected]> * Refs #19432: apply review suggestions Signed-off-by: JLBuenoLopez-eProsima <[email protected]> --------- Signed-off-by: JLBuenoLopez-eProsima <[email protected]>
eProsima · Sep 15, 2023 · d5f5ffd · d5f5ffd
1 parent 4609f24
commit d5f5ffd
Showing 1 changed file with 7 additions and 1 deletion.
diff --git a/docs/fastdds/discovery/discovery_server.rst b/docs/fastdds/discovery/discovery_server.rst
@@ -79,9 +79,15 @@ In this architecture there are several key concepts to understand:
     since several *servers* can be hosted in the same machine, thus having the same IP, and also because multicast
     addresses are acceptable addresses.
 
-- A |SUPER_CLIENT| is a *client* that receives all the discovery information known by the *server*, in opposition to
+- 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.
 
+  .. 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.
+    Any DomainParticipant discovered by the *Server* with no endpoints will not be known by the |SUPER_CLIENT|.
+
 - *Servers* do not require any beforehand knowledge of their *clients*, but their |GuidPrefix_t-api| and locator list
   (where they are listening) must match the one provided to the *clients*.
   *Clients* send discovery messages to the *servers* at regular intervals (ping period) until they receive message