LUDOC-296 protocol: remove internal details from descriptions

[doc/protocol.git] / connection.txt

diff --git a/connection.txt b/connection.txt
index cc0b739..fe6dd65 100644 (file)
--- a/connection.txt
+++ b/connection.txt
@@ -8,8 +8,8 @@ example of two such entities are a client and a target on some
 server. The target is identified by name to the client through an
 interaction with the management server. The client then 'connects' to
 the given target on the indicated server by sending the appropriate
-version of the *_CONNECT message (MGS_CONNECT, MDS_CONNECT, or
-OST_CONNECT - colectively *_CONNECT) and receiving back the
+version of the various *_CONNECT message (MGS_CONNECT, MDS_CONNECT, or
+OST_CONNECT) and receiving back the
 corresponding *_CONNECT reply. The server creates an 'export' for the
 connection between the target and the client, and the export holds the
 server state information for that connection. When the client gets the
@@ -22,7 +22,8 @@ There are also connections between the servers: Each MDS and OSS has a
 connection to the MGS, where the MDS (respectively the OSS) plays the
 role of the client in the above discussion. That is, the MDS initiates
 the connection and has an import for the MGS, while the MGS has an
-export for each MDS. Each MDS connects to each OST, with an import on
+export for each MDS. Each MDS creates an 'object storage proxy' (OSP)
+connection to each OST, with an import on
 the MDS and an export on the OSS. This connection supports requests
 from the MDS to the OST to create and destroy data objects, to set
 attributes (such as permission bits), and for 'statfs' information for
@@ -30,10 +31,10 @@ precreation needs.  Each OSS also connects to the first MDS to get
 access to auxiliary services, with an import on the OSS and an export
 on the first MDS.  The auxiliary services are: the File ID Location
 Database (FLDB), the quota master service, and the sequence
-controller. This connection for auxiliary services is a 'lightweight'
-one in that it has no replay functionality and consumes no space on
-the MDS for client data. Each MDS connects also to all other MDSs for
-DNE needs.
+controller. This connection for auxiliary services is a 'light weight
+proxy' (LWP) connection in that it has no replay functionality and
+consumes no space on the MDS for client data. Each MDS connects also
+to all other MDSs for DNE needs.
 
 Finally, for some communications the roles of message initiation and
 message reply are reversed. This is the case, for instance, with
@@ -43,11 +44,6 @@ other end of the connection maintains a 'reverse-import'. The
 reverse-import uses the same structure as a regular import, and the
 reverse-export uses the same structure as a regular export.
 
-#################################################################
-Fixme: Move the obd_connect_data.txt include to where it first
-gets introduced. Perhaps in obd_connect_client.txt?
-#################################################################
-
 include::obd_connect_data.txt[]
 
 include::import.txt[]