LUDOC-296 protocol: Rearrange presentation to be more top-down

[doc/protocol.git] / export.txt

diff --git a/export.txt b/export.txt
index 141d0d9..0b3797c 100644 (file)
--- a/export.txt
+++ b/export.txt
@@ -1,6 +1,7 @@
 Export
 ^^^^^^
 [[obd-export]]
+
 An 'obd_export' structure for a given target is created on a server
 for each client that connects to that target. The exports for all the
 clients for a given target are managed together. The export represents
@@ -14,6 +15,7 @@ the server can read the export data from disk to allow the client
 to reconnect and participate in recovery, otherwise a client without
 any export data will not be allowed to participate in recovery.
 
+[source,c]
 ----
 struct obd_export {
         struct portals_handle     exp_handle;
@@ -111,6 +113,8 @@ are further debug info that list the actual locks accounted for in
 ////^^^^
 //////////////////////////////////////////////////////////////////////
 
+include::struct_obd_uuid.txt[]
+
 The 'exp_client_uuid' holds the UUID of the client connected to this
 export.  This UUID is randomly generated by the client and the same
 UUID is used by the client for connecting to all servers, so that
@@ -203,6 +207,7 @@ in the connect messages passed between the hosts.
 //////////////////////////////////////////////////////////////////////
 ////vvvv
 The 'exp_flags' field encodes three directives as follows:
+[source,c]
 ----
 enum obd_option {
         OBD_OPT_FORCE =         0x0001,