jeena/GGS-report
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Revised entire chapter 5

Browse source
This commit is contained in:
Jonatan Pålsson 2011-05-12 22:47:44 +02:00
parent 64e43a0aad
commit 6bced613d0
1 changed files with 5 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

24
report.lyx
View file

@ -6060,8 +6060,9 @@ In Erlang, there is a simple version of supervisors.
No state of the processes being supervised is inspected. No state of the processes being supervised is inspected.
There is, however a specification of how the supervised processes should There is, however a specification of how the supervised processes should
behave, but on a higher level. behave, but on a higher level.
The specification describes things such as how many times in a given interval a child process may crash, which processes need restarting when The specification describes things such as how many times in a given interval
crashes occur, etc. a child process may crash, which processes need restarting when crashes
occur, etc.
\end_layout \end_layout
@ -6119,8 +6120,8 @@ reference "fig:The-supervisor-structure"
\begin_layout Standard \begin_layout Standard
A choice has been made to let faulty processes crash very easily when they A choice has been made to let faulty processes crash very easily when they
receive bad data, or something unexpected happens. receive bad data, or something unexpected happens.
The alternative to crashing would have been to try to fix this faulty The alternative to crashing would have been to try to fix this faulty data,
data, or to foresee the unexpected events. or to foresee the unexpected events.
This was not chosen since it is so simple to monitor and restart processes, This was not chosen since it is so simple to monitor and restart processes,
and so difficult to try to mend broken states. and so difficult to try to mend broken states.
This approach is something widely deployed in the Erlang world, and developers This approach is something widely deployed in the Erlang world, and developers
@ -8082,21 +8083,6 @@ textbf{ETS}}{Erlang Term Storage}
\end_layout \end_layout
\begin_layout Subsection
Documentation
\end_layout
\begin_layout Standard
To start the GGS is not self explanatory.
This together with overall usage of GGS should be documented.
The interface for usage of game developers are also in need of documentation.
Features and requirements with respect to the GGS would assist users to
know what they need to use the GGS and how they would benefit of it.
The GGS does not support many programming languages nor does it have a
complete documentation.
This needs to be taken care of in future versions.
\end_layout
\begin_layout Chapter \begin_layout Chapter
Conclusion Conclusion
\end_layout \end_layout