paragraphs in future, update on shares

[msc-thesis1617.git] / appendix-protocol.tex

diff --git a/appendix-protocol.tex b/appendix-protocol.tex
index 3936588..41e82d0 100644 (file)
--- a/appendix-protocol.tex
+++ b/appendix-protocol.tex
@@ -4,10 +4,34 @@ easier. Message exchanges have a \emph{Request} and \emph{Response} header.
 The \emph{Request} header means that the server is sending to the client. The
 \emph{Response} header means that the client is sending to the server. In some
 cases either the \emph{Request} or \emph{Response} is empty. This means that
-the message is not acknowledged or responded upon.
+the message is not acknowledged or responded upon. Multibyte values are
+interpreted as \gls{MSB} first integers.
 
 \section{Handshake}
-\todo{Handshake, here the client tells the server what they can do}
+\begin{table}[!ht]
+       \centering
+       \begin{subfigure}[t]{.48\textwidth}
+               \begin{tabular}{ll}
+                       \toprule
+                       \multicolumn{2}{c}{Request}\\
+                       byte & value\\
+                       \midrule
+                       1 & \texttt{'c'}\\
+                       \midrule\midrule
+                       \multicolumn{2}{c}{Response}\\
+                       byte & value\\
+                       \midrule
+                       1 & \texttt{'c'}\\
+                       2 & Peripheral bitmask\\
+                       3,4 & Bytes of memory\\
+                       5,6 & Size of the stack\\
+                       7 & Number of analog pins\\
+                       8 & Number of digital pins\\
+                       \bottomrule
+               \end{tabular}
+               \caption{Send a device specification}
+       \end{subfigure}
+\end{table}
 
 \newpage
 \section{mTasks}