From 6a87b1cf54885122a7fd6f9bb3b318c6a1b6d1cb Mon Sep 17 00:00:00 2001 From: Mart Lubbers Date: Mon, 19 Jun 2017 19:37:00 +0200 Subject: [PATCH] sweep part --- results.arch.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/results.arch.tex b/results.arch.tex index cbd0788..1c0f7f7 100644 --- a/results.arch.tex +++ b/results.arch.tex @@ -1,9 +1,9 @@ \section{Overview \& Terminology} The goal of the architecture is to facilitate an ecosystem in which an \gls{iTasks}-system can add, change and remove devices at runtime. Moreover, -the \gls{iTasks}-system can send \glspl{mTask}, compiled at runtime to -bytecode, to the device. The device runs an interpreter which can execute the -\gls{Task}'s bytecode. Devices are persistent during reboots of the +the \gls{iTasks}-system can send \glspl{mTask} --- compiled at runtime to +bytecode --- to the device. The device runs an interpreter which can execute +the \gls{Task}'s bytecode. Devices are persistent during reboots of the \gls{iTasks}-system. The methods of interacting with \glspl{mTask} is analogous to interacting with \gls{iTasks}-\glspl{Task} and programmers can access the \glspl{SDS} made for a device in the same way as a regular \glspl{SDS}. The -- 2.20.1