more text

[ri1617.git] / architecture / itasks.tex

diff --git a/architecture/itasks.tex b/architecture/itasks.tex
index acc5da1..cbda838 100644 (file)
--- a/architecture/itasks.tex
+++ b/architecture/itasks.tex
@@ -18,21 +18,10 @@ the task that can later on be used to kill a task even when it is not finished.
 During initialization the task value is \CI{NoValue}. When the initialization
 is done and the task is loaded the value becomes an unstable \CI{Int} value
 that denotes the task identification. When the task is finished the value
-becomes stable and no interaction can be done with the type from then on.
-
-\todo{Dit wat hieronder staat omschrijven}
-
-To make the integration of \mTask{}s in \iTasks{} more orthogonal we need a
-special kind of task that serves as a mothertask that has the type visible in
-Listing~\ref{lst:mothertask}. At first the system must be initialized with the
-first given function. This will setup the necessary communication tasks and
-SDSs used for interal storage and communication. This task is automatically
-started when the system boots up. To add a task one has to call \CI{addmTask}
-which will send the task to the system and evaluate it. Currently the only way
-of getting info back is through SDSs that are used in the \mTask. Some tasks
-are designed to run indefinite, for example temperature monitoring, and to
-remove them the \CI{delmTask} function is introduced that will remove the task
-and return a success value.
+becomes stable and no interaction can be done with the type from then on. Tasks
+can be deleted at runtime by using the \CI{delmTask} function that will return
+a task of type \CI{Bool} to indicate success. All type signatures are available
+in Listing~\ref{lst:mothertask}.
 
 \begin{lstlisting}[language=Clean,label={lst:mothertask}]
 mTask :: DeviceSpec -> Task ()