summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--notFinishedCode/Report/test.aux2
-rw-r--r--notFinishedCode/Report/test.log14
-rw-r--r--notFinishedCode/Report/test.pdfbin1473279 -> 1474457 bytes
-rw-r--r--notFinishedCode/Report/test.tex11
-rw-r--r--notFinishedCode/Report/test.tex.backup5
-rw-r--r--notFinishedCode/Report/test.tex~10
-rw-r--r--notFinishedCode/Report/test.toc2
7 files changed, 29 insertions, 15 deletions
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index 746c38b..b81fb06 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -51,9 +51,9 @@
\@writefile{toc}{\contentsline {section}{\numberline {6}Communication protocol}{17}}
\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Handler side}{17}}
\@writefile{lof}{\contentsline {figure}{\numberline {14}{\ignorespaces }}{17}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{17}}
\@writefile{lof}{\contentsline {figure}{\numberline {15}{\ignorespaces }}{18}}
\@writefile{lof}{\contentsline {figure}{\numberline {16}{\ignorespaces }}{18}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{18}}
\citation{sshTunnel}
\@writefile{toc}{\contentsline {section}{\numberline {7}Security and safety of the system}{20}}
\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{20}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index fdfbb8e..1898d41 100644
--- a/notFinishedCode/Report/test.log
+++ b/notFinishedCode/Report/test.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 22 OCT 2011 17:57
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 22 OCT 2011 21:15
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -386,17 +386,17 @@ File: sshTunnel.png Graphic file (type png)
<use sshTunnel.png> [20
<./sshTunnel.png (PNG copy)>] [21] [22]
-LaTeX Font Info: Try loading font information for OMS+cmr on input line 524.
+LaTeX Font Info: Try loading font information for OMS+cmr on input line 529.
(/usr/share/texmf-texlive/tex/latex/base/omscmr.fd
File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 524.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 529.
[23] [24] [25]
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 596.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 601.
<resultsImage.png, id=118, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
@@ -410,7 +410,7 @@ Here is how much of TeX's memory you used:
8054 multiletter control sequences out of 15000+50000
17720 words of font info for 42 fonts, out of 3000000 for 9000
28 hyphenation exceptions out of 8191
- 36i,11n,45p,760b,1685s stack positions out of 5000i,500n,10000p,200000b,50000s
+ 36i,11n,45p,760b,1683s stack positions out of 5000i,500n,10000p,200000b,50000s
</home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm090
0.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm0600.600pk> </
home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm0800.600pk> </home/refik/
@@ -425,9 +425,9 @@ r/fonts/pk/ljfour/jknappen/ec/ecrm1728.600pk></usr/share/texmf-texlive/fonts/ty
pe1/public/amsfonts/cm/cmmi10.pfb></usr/share/texmf-texlive/fonts/type1/public/
amsfonts/cm/cmsy10.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm
/cmsy9.pfb>
-Output written on test.pdf (29 pages, 1473279 bytes).
+Output written on test.pdf (29 pages, 1474457 bytes).
PDF statistics:
- 686 PDF objects out of 1000 (max. 8388607)
+ 689 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
96 words of extra memory for PDF output out of 10000 (max. 10000000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index 95dff4e..cd1017b 100644
--- a/notFinishedCode/Report/test.pdf
+++ b/notFinishedCode/Report/test.pdf
Binary files differ
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index dfcc87f..ce8e7a1 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -319,9 +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}.
-Thereupon, after the message has been validated the handler side sends the controller side a response, \emph{HELLO CONTROLLER}.
+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}
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 8cecd2c..dfcc87f 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -318,7 +318,10 @@ that physically handles the call (e.g. the BeagleBoard) whereas the controller (
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 it is waiting for a connection to accept at the defined port.
+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}.
+Thereupon, after the message has been validated the handler side sends the controller side a response, \emph{HELLO CONTROLLER}.
\begin{figure}[ht!]
\centering
\includegraphics[width=130mm]{protocolCommunicationHandler.png}
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}
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index fb9be1e..a27dd04 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -19,7 +19,7 @@
\contentsline {subsection}{\numberline {5.4}Server}{16}
\contentsline {section}{\numberline {6}Communication protocol}{17}
\contentsline {subsection}{\numberline {6.1}Handler side}{17}
-\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{17}
+\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{18}
\contentsline {section}{\numberline {7}Security and safety of the system}{20}
\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{20}
\contentsline {subsection}{\numberline {7.2}Security on the web site}{21}