From 89ec38819f77258b6ecbdecfd0e594e56eb1c48b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 21:47:31 +0200 Subject: [PATCH 1/2] Revised 3.4.1 --- report.lyx | 64 ++++++++++++++++++++++++++++++++++-------------------- 1 file changed, 41 insertions(+), 23 deletions(-) diff --git a/report.lyx b/report.lyx index a7bfc95..a882b28 100644 --- a/report.lyx +++ b/report.lyx @@ -5206,12 +5206,20 @@ Callbacks written in Erlang are registered to the VM for the interface to the game state and send messages to the clients. The interface provides access to three objects called \emph on -world, players +\noun on +world +\noun default +, +\noun on +players \emph default +\noun default and \emph on +\noun on localStorage \emph default +\noun default . The game state is safely stored in a database and retrieved for manipulation by a call for the world object. @@ -5286,7 +5294,14 @@ name "sub:Exposing-Erlang-functionality" \end_layout \begin_layout Standard -This section contains a concrete example of how the localstorage and world +This section contains a concrete example of how the +\noun on +localStorage +\noun default + and +\noun on +world +\noun default objects are exposed to a GDL VM. The example comes from the GGS prototype, which uses JavaScript powered by Google V8 as its GDL VM. @@ -5358,16 +5373,33 @@ tt GGS.localStorage } \end_inset - from within the GDL, access to the localstorage is provided, thus the localstor -age must be connected to the GGS object, this can be seen in line 5. + from within the GDL, access to the +\noun on +localStorage +\noun default + is provided, thus the +\noun on +localStorage +\noun default + must be connected to the GGS object, this can be seen in line 5. \end_layout \begin_layout Standard -Both the GGS and localstorage objects are dummy objects, which provide no - functionality, these two objects are simply placed in the GDL for the purpose - clearing up the code. - In order to perform an action using the GGS and localstorage objects, the - +Both the +\noun on +GGS +\noun default + and +\noun on +localStorage +\noun default + objects are dummy objects, which provide no functionality, these two objects + are simply placed in the GDL for the purpose clearing up the code. + In order to perform an action using the GGS and +\noun on +localStorage +\noun default + objects, the \begin_inset ERT status open @@ -5443,20 +5475,6 @@ tt setTimeout} per default. \end_layout -\begin_layout Standard -\begin_inset Note Note -status open - -\begin_layout Plain Layout -Prior to this section, the Erlang syntax has to be briefly explained. - I think the 'usage of erlang' section is a good place to do this in. -\end_layout - -\end_inset - - -\end_layout - \begin_layout Standard \begin_inset Float algorithm wide false From e099c26937f003a355a21c898f4c1852587a1d74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 21:56:38 +0200 Subject: [PATCH 2/2] Revised 3.5 --- report.lyx | 47 +++++++++++++++++++++++++---------------------- 1 file changed, 25 insertions(+), 22 deletions(-) diff --git a/report.lyx b/report.lyx index 725f32b..e3b442c 100644 --- a/report.lyx +++ b/report.lyx @@ -5846,24 +5846,12 @@ Techniques for ensuring reliability \begin_layout Standard One of the main goals of the project is to achieve high reliability. - The term -\begin_inset Quotes eld -\end_inset + The term 'reliable system' is defined by the IEEE as +\end_layout -reliable system -\begin_inset Quotes erd -\end_inset - - is defined by the IEEE as a system with -\begin_inset Quotes eld -\end_inset - -the ability of a system or component to perform its required functions under - stated conditions for a specified period of time -\begin_inset Quotes erd -\end_inset - - +\begin_layout Quotation +A system with the ability of a system or component to perform its required + functions under stated conditions for a specified period of time \begin_inset CommandInset citation LatexCommand citet key "ieee_90" @@ -5871,10 +5859,13 @@ key "ieee_90" \end_inset . - There are some tools for creating reliable applications built in to Erlang. +\end_layout + +\begin_layout Standard +There are some tools for creating reliable applications built in to Erlang: \begin_inset ERT -status open +status collapsed \begin_layout Plain Layout @@ -5902,14 +5893,22 @@ E"} \end_layout \begin_layout Itemize -Links between processes. + +\series bold +Links between processes +\series default +. When a process spawns a new child process, and the child process later exits, the parent process is notified of the exit. \end_layout \begin_layout Itemize -Transparent distribution over a network of processors. + +\series bold +Transparent distribution over a network of processors +\series default +. When several nodes participate in a network, it does not matter on which of these machines a process is run. Communication between processes does not depend on the node in which each @@ -5918,7 +5917,11 @@ Transparent distribution over a network of processors. \end_layout \begin_layout Itemize -Hot code replacements. + +\series bold +Hot code replacements +\series default +. Two versions of the same module can reside in the memory of Erlang at any time. This means that a simple swap between these versions can take place very