system.tex

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