diff --git a/doc/lab0.pdf b/doc/lab0.pdf index 836b5d58779929c8dd819cef57952f88deb157a9..67918a15c4bda8d43f535c0ce54dd7f0de22bcf8 100644 Binary files a/doc/lab0.pdf and b/doc/lab0.pdf differ diff --git a/doc/lab0.tex b/doc/lab0.tex index aeafb4e27619214c47c95edcc0c7aee6eeeb0d62..78c94bc824b9a789c2969f89f6150286ec9636df 100644 --- a/doc/lab0.tex +++ b/doc/lab0.tex @@ -167,6 +167,25 @@ you should complete the implementation of the following three function in \end{itemize} Recall the note at the end of \sref{data-format}. +\subsection{Additional questions} +When demonstrating this lab (as with any lab in the course), you +should be able to explain your code, but also to evaluate it, and +relate it to course concepts. In many cases this will involve +discussing design choices and simplifications that have been made for +you, and may be somewhat speculative. In some cases you might be asked +to answer questions with (at least in retrospect) quite obvious +answers. In this lab, this might include questions such as + +\begin{itemize} + \item Thinking about the boundaries of the system: what happens if + two processes try to write to the database at the same time? Is + this something that we need to handle? +\end{itemize} + +We do not require written answers to this, and you might not need to +provide a solution to all issues raised by the questions. + + \section{Conclusion} Having completed the lab, you can now perform the reading and writing operations on the database. However, if you run several instances of the application on