arch.tex

   1 The system provides a framework of functions with
   2 which an \gls{iTasks}-system can add, change and remove devices at runtime.
   3 Moreover, the \gls{iTasks}-system can send \gls{mTask}-\glspl{Task} ---
   4 compiled at runtime to bytecode by the \gls{mTask}-view --- to the device. The
   5 device runs an interpreter which executes the \gls{Task}'s bytecode following
   6 the scheduling strategy given. Devices added to the system are stored and get a
   7 profile for identification. These profiles are persistent during reboots of
   8 the \gls{iTasks}-system to allow for easy reconnecting with old devices. The
   9 methods of interacting with \gls{mTask}-\gls{Task} is analogous to interacting
  10 with \gls{iTasks}-\glspl{Task}. This means that programmers can access the
  11 \glspl{SDS} made for a device in the same way as regular \glspl{SDS} and they
  12 can execute \gls{mTask}-\glspl{Task} as if they where normal
  13 \gls{iTasks}-\glspl{Task}.
  14
  15 \section{Devices}
  16 \input{arch.devices}
  17
  18 \section{iTasks}
  19 \input{arch.itasks}
  20
  21 \section{Communication}
  22 \input{arch.communication}
  23
  24 \section[Lifting mTasks to iTasks-Tasks]%
  25         {Lifting \gls{mTask}-\glspl{Task} to \gls{iTasks}-\glspl{Task}}
  26 \input{arch.lift}
  27
  28 \section{Example}
  29 \input{arch.example}