shares

[msc-thesis1617.git] / results.itasks.tex

diff --git a/results.itasks.tex b/results.itasks.tex
index 4cbc80e..7a87936 100644 (file)
--- a/results.itasks.tex
+++ b/results.itasks.tex
@@ -1,8 +1,67 @@
-\subsection{Shares}
-\todo{Semantiek van shares, hoe ze in iTasks zijn, hoe typering}
+The glue in the system is written in \gls{iTasks}. Functions for managing
+devices, \glspl{Task} and \glspl{SDS} are created. An interface is made that
+allows an interactive management console for the \gls{mTask} system. This
+interface provides functionality to list shares, add tasks, remove tasks,
+administrate devices and view the state of the system.
+
+\section{Integration}
+When the system starts up the devices residing in the \gls{SDS} must be cleaned
+up. It might be the case that they contain tasks, shares or errors. A user or
+programmer can then choose to reconnect some devices using the
+\CI{connectDevice} function.
+
+\begin{lstlisting}[caption={Starting up the devices},%
+       label={lst:startupdevs}]
+startupDevices :: Task [MTaskDevice]
+startupDevices = upd (map reset) deviceStoreNP
+       where reset d = {d & deviceTask=Nothing, deviceTasks=[], deviceError=Nothing}
+\end{lstlisting}
+
+An image of the management interface is shown in Figure~\ref{lst:manage}.
+The system management is done by a single \gls{Task} called \CI{mTaskManager}.
+To manage the system, a couple of different functionalities are needed and
+are launched. The left sidebar of the interface shows the list of example
+\glspl{Task} that are present in the system. When clicking a task, a dialog
+opens in which you can select the device to send the task to.  The dialog might
+contain user specified variables. All example \glspl{mTask} are of the type
+\CI{Task (Main (ByteCode () Stmt))} and can thus ask for user input first.
+
+The bottom panel shows the device information. In this panel, the devices can
+be created and modified. Moreover, this panel allows the user to reconnect with
+a device after a restart of the server application.
+
+\begin{figure}[H]
+       \centering
+       \includegraphics[width=\linewidth]{manage}
+       \caption{The device management interface}\label{lst:management}
+\end{figure}
 
-\subsection{Lifting}
-\todo{Lift mTask taken naar echte taken, hoe werkt dat?}
+\section{Shares}
+The architecture of the system stores the \glspl{SDS} in the \gls{SDS} that
+stores the list of devices. This means that if a \gls{SDS} updates, everyone
+watching it will be notified. This would result in to a lot of notifications
+that are not ment to be for the listener. Moreover, when a client updates the
+\gls{SDS} this is processed by the connection handler and results in an update
+of the real \gls{SDS}. When an \gls{iTasks}-\gls{Task} writes to a \gls{SDS}
+this is not passed on to the device.
 
-\section{Demo}
-\todo{Wat voorbeeld code}
+To solve the problem, parametric lenses are used on the device storage.
+Listing~\ref{lst:actualdev} shows the actual types for the device storage.
+Programmers wanting to access the entire \gls{SDS} use the \CI{deviceStoreNP}.
+Programmers wanting to access a single \gls{SDS} on a device can use the
+\CI{getRealShare} function which is a wrapper around the \CI{deviceStore} which
+applies a parametric lens.
+
+\begin{lstlisting}[label={lst:actualdev},%
+       caption={Real types for the device \gls{SDS}}]
+deviceStoreNP :: Shared [MTaskDevice]
+deviceStore :: RWShared (Maybe (MTaskDevice, Int)) [MTaskDevice] [MTaskDevice]
+
+realDeviceStore :: Shared [MTaskDevice]
+
+getRealShare :: MTaskDevice MTaskShare -> Shared BCValue
+\end{lstlisting}
+
+\subsection{Parametric Lens}
+Therefore the main device store 
+\todo{Semantiek van shares, hoe ze in iTasks zijn, hoe typering}