summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex~
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-22 21:15:43 +0200
committerRefik Hadzialic2011-10-22 21:15:43 +0200
commitacc00089654b8145b57f40e376378e2db16b6d63 (patch)
tree9d3edd679d746d1d71b1364f8d4096e08254e9f9 /notFinishedCode/Report/test.tex~
parentReport writing (diff)
downloadgsm-selftest-acc00089654b8145b57f40e376378e2db16b6d63.tar.gz
gsm-selftest-acc00089654b8145b57f40e376378e2db16b6d63.tar.xz
gsm-selftest-acc00089654b8145b57f40e376378e2db16b6d63.zip
Report writing
Diffstat (limited to 'notFinishedCode/Report/test.tex~')
-rw-r--r--notFinishedCode/Report/test.tex~10
1 files changed, 8 insertions, 2 deletions
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index b7364d9..ce8e7a1 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -319,8 +319,14 @@ controlling the handler side and assigning the task to it.
\subsection{Handler side}
The handler side is always in the waiting mode, by waiting we denote the mode where the socket is already created and it is waiting
-for a connection to be accepted at the defined port. Subsequently, after the connection has been established, it is waiting for a
-message to be received. The first message has to be 13 characters long and include the following content \emph{HELLO HANDLER}.
+for a connection to be accepted at the defined port. The controller initiates a socket connection to the two handlers.
+Subsequently, after the connection has been established, it is waiting for a message to be received. The first message
+has to be 13 characters long and include the following content \emph{HELLO HANDLER}. Thereupon, after the message has
+been validated, the handler side sends the controller side a response, \emph{HELLO CONTROLLER}.
+We call this first message exchange the initialization. Now the controller side has to decide which of the two handler's
+will be the caller/callee whereas the other handler will be the opposite. Let's assume the controller sends to the first
+handler the message \emph{RECEIVER} and to the second one the message \emph{CALLER|\#}
+
\begin{figure}[ht!]
\centering
\includegraphics[width=130mm]{protocolCommunicationHandler.png}