* Security
** TODO Implement SMACK based access control.
   Currently any application may connect to the settings daemon's web
   socket, and invoke operations.  This is of course a security hole
   that needs to be closed.  To do that a SMACK based approach should
   employed to limit access to authorized applications, such as the
   settings app.  However, this is not straightforward for Web apps
   since they all run in the same domain.  A policy framework is
   currently being discussed to address this issue.

* Concurrency
** TODO Determine if it makes sense to make the settings daemon multithreaded.

* Miscellaneous
** TODO Validate websocket server port chosen by user.