elaborate on comm

[msc-thesis1617.git] / arch.communication.tex

diff --git a/arch.communication.tex b/arch.communication.tex
index 7da8ad1..1e9b4b6 100644 (file)
--- a/arch.communication.tex
+++ b/arch.communication.tex
@@ -2,8 +2,8 @@ The communication from the server to the client and vice versa is just a
 character stream containing encoded \gls{mTask} messages. The \CI{synFun}
 belonging to the device is responsible for sending the content in the left
 channel and putting received messages in the right channel. Moreover, the
-boolean value should be set to \CI{True} when the connection is terminated. The
-specific encoding of the messages is visible in
+boolean flag in the channel type should be set to \CI{True} when the connection
+is terminated. The specific encoding of the messages is visible in
 Appendix~\ref{app:communication-protocol}. The type holding the messages is
 shown in Listing~\ref{lst:avmsg}. Detailed explanation about the message types
 and according actions will be given in the following subsections.
@@ -51,7 +51,6 @@ brevity.
        }
 \end{lstlisting}
 
-
 \subsection{Add a device}
 A device can be added by filling in the \CI{MTaskDevice} record as much as
 possible and running the \CI{connectDevice} function. This function grabs the
@@ -121,7 +120,7 @@ channel \gls{SDS} of the device. This will result in sending the actual
 \gls{SDS} specification and \gls{Task} specifications to the device. A
 \gls{Task} record is created with the identifier $-1$ to denote a \gls{Task}
 not yet acknowledged. Finally the device itself is updated with the new state
-and with the new \gls{Task}.  After waiting for the acknowledgement the device
+and with the new \gls{Task}. After waiting for the acknowledgement the device
 is updated again and the \gls{Task} returns.
 
 \begin{lstlisting}[label={lst:sendtask},%