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 or interrupt\\
24 4,
5 & length (
\texttt{n
})\\
27 \multicolumn{2}{c
}{Response
}\\
37 \begin{subfigure
}[t
]{.48\textwidth}
40 \multicolumn{2}{c
}{Request
}\\
46 \multicolumn{2}{c
}{Response
}\\
53 \caption{Delete a task
}
55 \caption{Message protocol for exchanging tasks
}
61 \begin{subfigure
}[t
]{.2\textwidth}
64 \multicolumn{2}{c
}{Request
}\\
71 \multicolumn{2}{c
}{Response
}\\
78 \caption{Send an SDS specification
}
81 \begin{subfigure
}[t
]{.2\textwidth}
84 \multicolumn{2}{c
}{Response
}\\
90 \multicolumn{2}{c
}{Request
}\\
97 \caption{Delete a SDS
}
100 \begin{subfigure
}[t
]{.2\textwidth}
103 \multicolumn{2}{c
}{Request
}\\
110 \multicolumn{2}{c
}{Response
}\\
116 \begin{subfigure
}[t
]{.2\textwidth}
119 \multicolumn{2}{c
}{Response
}\\
121 \multicolumn{2}{c
}{Request
}\\
129 \caption{SDS publish
}
131 \caption{Message protocol for exchanging SDSs
}