From d5f5ffd90ce5f6c5b222127cf36b40f4c2e92a8a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jos=C3=A9=20Luis=20Bueno=20L=C3=B3pez?= <69244257+JLBuenoLopez-eProsima@users.noreply.github.com> Date: Fri, 15 Sep 2023 10:23:40 +0200 Subject: [PATCH] Clarify super client discovery information (#555) * Refs #19432: clarify super client discovery information Signed-off-by: JLBuenoLopez-eProsima * Refs #19432: apply review suggestions Signed-off-by: JLBuenoLopez-eProsima --------- Signed-off-by: JLBuenoLopez-eProsima --- docs/fastdds/discovery/discovery_server.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/fastdds/discovery/discovery_server.rst b/docs/fastdds/discovery/discovery_server.rst index 01bad8704..9881e94f1 100644 --- 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