1 \section{General message format
}
2 Messages are delimited by newlines to make processing by line based devices
3 more easy. Message exchanges have a
\emph{Request
} and
\emph{Response
} header.
4 The
\emph{Request
} header means that the server is sending to the client. The
5 \emph{Response
} header means that the client is sending to the server. In some
6 cases either the
\emph{Request
} or
\emph{Response
} is empty. This means that
7 the message is not acknowledged or responded upon.
10 \todo{Handshake, here the client tells the server what they can do
}
16 \begin{subfigure
}[t
]{.48\textwidth}
19 \multicolumn{2}{c
}{Request
}\\
23 2,
3 & interval. If the first bit is
1 the other
15 indicate the
24 interrupt on which the task should be run. If the first bit is
0
25 the other
15 indicate the interval in milliseconds\\
26 4,
5 & length (
\texttt{n
})\\
29 \multicolumn{2}{c
}{Response
}\\
39 \begin{subfigure
}[t
]{.48\textwidth}
42 \multicolumn{2}{c
}{Request
}\\
48 \multicolumn{2}{c
}{Response
}\\
55 \caption{Delete a task
}
57 \caption{Message protocol for exchanging tasks
}
63 \begin{subfigure
}[t
]{.2\textwidth}
66 \multicolumn{2}{c
}{Request
}\\
73 \multicolumn{2}{c
}{Response
}\\
80 \caption{Send an SDS specification
}
83 \begin{subfigure
}[t
]{.2\textwidth}
86 \multicolumn{2}{c
}{Response
}\\
92 \multicolumn{2}{c
}{Request
}\\
99 \caption{Delete a SDS
}
102 \begin{subfigure
}[t
]{.2\textwidth}
105 \multicolumn{2}{c
}{Request
}\\
112 \multicolumn{2}{c
}{Response
}\\
118 \begin{subfigure
}[t
]{.2\textwidth}
121 \multicolumn{2}{c
}{Response
}\\
123 \multicolumn{2}{c
}{Request
}\\
131 \caption{SDS publish
}
133 \caption{Message protocol for exchanging SDSs
}