of regular \gls{iTasks}-\glspl{SDS}. However, the same freedom that an
\gls{SDS} has in the \gls{iTasks}-system is not given for \glspl{SDS} that
reside on the client. Not all types are suitable to be located on a client,
-simply because it needs to be representable on clients. Moreover, \glspl{SDS}
-behave a little different in an \gls{mTask} device compared to in the
-\gls{iTasks} system. In an \gls{iTasks} system, when the \gls{SDS} is updated,
-a broadcast to all watching \glspl{Task} in the system is made to notify them
-of the update. \glspl{SDS} can update often and the update might not be the
-final value it will get. Implementing the same functionality on the \gls{mTask}
-client would result in a lot of expensive unneeded bandwidth usage. Therefore
-a device must publish the \gls{SDS} explicitly to save bandwidth. Note that
-this means that the \gls{SDS} value on the device can be different compared to
-the value of the same \gls{SDS} on the server.
+simply because it needs to be representable on clients. Also, not all \gls{SDS}
+types are possible to have on a device. Moreover, \glspl{SDS} behave a little
+different in an \gls{mTask} device compared to in the \gls{iTasks} system. In
+an \gls{iTasks} system, when the \gls{SDS} is updated, a broadcast to all
+watching \glspl{Task} in the system is made to notify them of the update.
+\glspl{SDS} can update often and the update might not be the final value it
+will get. Implementing the same functionality on the \gls{mTask} client would
+result in a lot of expensive unneeded bandwidth usage. Therefore a device must
+publish the \gls{SDS} explicitly to save bandwidth. Note that this means that
+the \gls{SDS} value on the device can be different compared to the value of the
+same \gls{SDS} on the server.
To add this functionality, the \CI{sds} class could be extended. However, this
would result in having to update all existing views that use the \CI{sds}
repositories / msc-thesis1617.git / blobdiff