system.tex

   1 The proposed system provides a bridge between the gap present in the current
   2 system. It provides a framework to offer functionality for an \gls{iTasks}
   3 server to outsource \glspl{Task} to \gls{IoT}-devices without needing to
   4 recompile the code. The \glspl{Task} are compiled to bytecode and interpreted
   5 on the client.
   6
   7 The following terms will be used throughout the following chapters:
   8 \begin{itemize}
   9         \item Device, Client
  10
  11                 These terms denotes the actual device connected to the system. This can
  12                 be a real device such as a microcontroller but it can also just be a
  13                 program on the same machine as the server functioning as a client.
  14         \item Server, \gls{iTasks}-System
  15
  16                 This is the actual executable serving the \gls{iTasks} application. The
  17                 system contains \glspl{Task} taking care of the communication with the
  18                 clients.
  19         \item System
  20
  21                 The system describes the complete ecosystem, containing both the server
  22                 and the clients including the communication between them.
  23         \item Engine
  24
  25                 The runtime system of the client is called the engine. This program
  26                 handles communicating with the server and runs the interpreter for the
  27                 \glspl{Task} on the client.
  28 \end{itemize}
  29
  30 \section{EDSL for IoT Tasks}
  31 \input{system.edsl}
  32
  33 \section{System Overview}
  34 \input{system.overview}