From acc00089654b8145b57f40e376378e2db16b6d63 Mon Sep 17 00:00:00 2001 From: Refik Hadzialic Date: Sat, 22 Oct 2011 21:15:43 +0200 Subject: Report writing --- notFinishedCode/Report/test.tex~ | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'notFinishedCode/Report/test.tex~') 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} -- cgit v1.2.3-55-g7522