system.tex

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