summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-22 16:19:25 +0200
committerRefik Hadzialic2011-10-22 16:19:25 +0200
commit0137535058d94844ed09c8980067c3159f1d68a4 (patch)
tree09aa53defd75e5200976c551fea397070fcec6d7 /notFinishedCode/Report/test.tex
parentRerport writing (diff)
downloadgsm-selftest-0137535058d94844ed09c8980067c3159f1d68a4.tar.gz
gsm-selftest-0137535058d94844ed09c8980067c3159f1d68a4.tar.xz
gsm-selftest-0137535058d94844ed09c8980067c3159f1d68a4.zip
Rerport writing
Diffstat (limited to 'notFinishedCode/Report/test.tex')
-rw-r--r--notFinishedCode/Report/test.tex7
1 files changed, 7 insertions, 0 deletions
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 8f684a3..38e4a52 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -307,6 +307,13 @@ We were given an old Pentium 3 computer where we installed Ubuntu Linux. Configu
\clearpage
\section{Communication protocol}
+A communication protocol represents a set of well defined rules by whose help two or more computing systems exchange information inbetween.
+When defining these rules, it is important to define a limited state space for every possible event, no matter did we get the appropriate
+response from the other side. Our approch to this problem was to build a simple synchronous protocol, where every expected message is
+confirmed or otherwise the connection between two sides is immediatelly terminated. Since designing protocols is a demanding and challenging
+topic which requires years of experience and verification, we do not expect that we had developed the best possible and an optimum protocol.
+In the following paragraphs we will try to give you a brief introduction of how our protocol works.
+
\subsection{Handler side}
\begin{figure}[ht!]
\centering