First a fresh identifier for the task is generated using the device state.
With this identifier, the cleanup hook can be installed.
This is done to assure the task is removed from the edge device if the \gls{ITASK} task coordinating it is destroyed.
-Tasks in \gls{ITASK} are destroyed when for example it is executed in parallel with another task and the parallel combinator terminates, or when the condition to step holds in a sequential task combination.
+Tasks in \gls{ITASK} are destroyed when for example they are executed in parallel with another task and the parallel combinator terminates, or when the condition to step holds in a sequential task combination.
Then the \gls{MTASK} compiler is invoked, its only argument besides the task is a function doing something with the results of the compilation, i.e.\ the lowered \glspl{SDS} and the messages containing the compiled and serialised task.
With the result of the compilation, the task can be executed.
First the messages are put in the channels, sending them to the device.
\section{Home automation}
This section presents an interactive home automation program (\cref{lst:example_home_automation}) to illustrate the dynamic integration of the \gls{MTASK} language and the \gls{ITASK} system.
All layers of \gls{IOT} systems are used in this application.
-The presentation layer consists of an automatically generated web interface for the user to control which tasks sent to a device for execution.
+The presentation layer consists of an automatically generated web interface for the user to control which tasks are sent to a device for execution.
The application layer is the \gls{ITASK} server, the coordinator of the tasks in the system that also stores the data.
The perception layer is populated by two devices: an \gls{ARDUINO} UNO, and an ESP8266 based prototyping board called {NodeMCU}.
\Crefrange{lst:example:spec1}{lst:example:spec2} show the specification for the devices.
repositories / phd-thesis.git / blobdiff