\section{General message format}
Messages are delimited by newlines to make processing by line based devices
-more easy. Message exchanges have a \emph{Request} and \emph{Response} header.
+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
byte & value\\
\midrule
1 & \texttt{'t'}\\
- 2,3 & interval\\
+ 2,3 & interval or interrupt\\
4,5 & length (\texttt{n})\\
6 to n+6 & bytecode\\
\midrule\midrule
byte & value\\
\midrule
1 & \texttt{'t'}\\
- 2,3 & task id\\
+ 2,3 & \gls{Task} id\\
\bottomrule
\end{tabular}
- \caption{Send a task}
+ \caption{Send a \gls{Task}}
\end{subfigure}
\quad%
\begin{subfigure}[t]{.48\textwidth}
byte & meaning\\
\midrule
1 & \texttt{'d'}\\
- 2,3 & task id\\
+ 2,3 & \gls{Task} id\\
\midrule\midrule
\multicolumn{2}{c}{Response}\\
byte & value\\
\midrule
1 & \texttt{'d'}\\
- 2,3 & task id\\
+ 2,3 & \gls{Task} id\\
\bottomrule
\end{tabular}
- \caption{Delete a task}
+ \caption{Delete a \gls{Task}}
\end{subfigure}
- \caption{Message protocol for exchanging tasks}
+ \caption{Message protocol for exchanging \glspl{Task}}
\end{table}
\section{SDSs}