From a9d0d8735e83093cc14d9c4bb0f5e16a51dfd555 Mon Sep 17 00:00:00 2001 From: Jeena Paradies Date: Thu, 12 May 2011 13:03:24 +0200 Subject: [PATCH 1/2] changed 2.5 --- bibliography.bib | 8 ++++++ report.lyx | 72 ++++++++++++++++++++++++++++++++++-------------- 2 files changed, 59 insertions(+), 21 deletions(-) diff --git a/bibliography.bib b/bibliography.bib index 447e8fe..0eaaa2b 100644 --- a/bibliography.bib +++ b/bibliography.bib @@ -192,6 +192,14 @@ URL = "http://www.theesa.com/facts/index.asp" } +@article {Dictionary.com2011, + title = {Merriam-Webster's Dictionary}, + month = {May}, + day = {12}, + year = {2011}, + url = {http://dictionary.reference.com/browse/fault+tolerance}, +} + @article{Armstrong:2010:ERL:1810891.1810910, author = {Armstrong, Joe}, diff --git a/report.lyx b/report.lyx index 10c819b..6d5fe94 100644 --- a/report.lyx +++ b/report.lyx @@ -2306,7 +2306,7 @@ The GGS is a game server. A game should not only be able to vary in terms of genre, graphics, gameplay etc, but also in the way the game is implemented for example in different programming languages. - The GGS should be OS independent and run on Windows, OSX and Linux. + The GGS should be OS independent and run on Windows, OS X and Linux. The GGS can be run as a listen server on the players computer and host games locally. It could also be a dedicated server running on dedicated independent hardware. @@ -2315,18 +2315,29 @@ The GGS is a game server. \end_layout \begin_layout Standard -Another aspect was the desire to let a client upload the source code of - the game it would like to play on the GGS. +Another aspect is the desire to let a client upload the source code of the + game it would like to play on the GGS. This way every client could connect to the server and install the game - through a -\begin_inset CommandInset nomenclature -LatexCommand nomenclature -symbol "API" -description "Application programming interface" + through a API without the need of installation through the server provider + or maintainer. +\end_layout + +\begin_layout Standard +\begin_inset ERT +status open + +\begin_layout Plain Layout + + +\backslash +nomenclature{ +\backslash +textbf{API}}{Application programming interface} +\end_layout \end_inset - without the need of installation through the server provider or maintainer. + \end_layout \begin_layout Section @@ -2341,17 +2352,36 @@ name "sec:Fault-Tolerance" \end_layout \begin_layout Standard -Fault tolerance is an important factor in all servers, a server that is - fault tolerant should be able to follow a given specification when parts - of the system fails. +Merriam-Webster’s dictionary +\begin_inset CommandInset citation +LatexCommand citeyearpar +key "Dictionary.com2011" + +\end_inset + + defines fault tolerance as: +\end_layout + +\begin_layout Quotation +1. + The ability of a system or component to continue normal operation despite + the presence of hardware or software faults. + This often involves some degree of redundancy. +\end_layout + +\begin_layout Quotation +2. + The number of faults a system or component can withstand before normal + operation is impaired. + +\end_layout + +\begin_layout Standard +Fault tolerance is an important factor in servers, a server that is fault + tolerant should be able to follow a given specification when parts of the + system fail. This means that fault tolerance is different in each system depending on - what specification they have. - A system could be fault tolerant in different aspects, one is where the - system is guaranteed to be available but not safe and it could also be - reversed, that the system is safe but not guaranteed to be available. - Depending on the system one property may be more important. - A system could also have non existent fault tolerance or it could be both - safe and guaranteed to be available. + what specification it has. It should be noted that it is not possible to achieve complete fault tolerance, a system will always have a certain risk of failure. With this in mind the goal is to make the GGS prototype as fault tolerant @@ -2361,8 +2391,8 @@ Fault tolerance is an important factor in all servers, a server that is \begin_layout Standard In order to make the GGS prototype fault tolerant the programming language Erlang has been used. - Erlang will not guarantee a fault tolerant system but it has features that - support and encourage the development of fault tolerant systems. + Erlang will not guarantee a fault tolerant system however it has features + that support and encourage the development of fault tolerant systems. In the GGS it is important that the system overall is fault tolerant and not small parts only. Crashes of the whole system should be avoided as this would make the system From a7f5051ab9ae49482529f0b84b4ce591a8855b0b Mon Sep 17 00:00:00 2001 From: Jeena Paradies Date: Thu, 12 May 2011 13:05:27 +0200 Subject: [PATCH 2/2] language changes in 2.5 --- report.lyx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/report.lyx b/report.lyx index 6d5fe94..5bc64cc 100644 --- a/report.lyx +++ b/report.lyx @@ -2391,14 +2391,14 @@ Fault tolerance is an important factor in servers, a server that is fault \begin_layout Standard In order to make the GGS prototype fault tolerant the programming language Erlang has been used. - Erlang will not guarantee a fault tolerant system however it has features + Erlang will not guarantee a fault tolerant system, however it has features that support and encourage the development of fault tolerant systems. - In the GGS it is important that the system overall is fault tolerant and - not small parts only. + In the GGS it is important that the complete system is fault tolerant, + not only small parts. Crashes of the whole system should be avoided as this would make the system unusable for a time. By using supervisor structures it is possible to crash and restart small - parts of the system, this is convenient as fault can be handled within + parts of the system, this is convenient as faults can be handled within small modules thus never forcing a crash of the system. \end_layout