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

Merge branch 'master' of github.com:jeena/GGS-report

Browse source
This commit is contained in:
Jonatan Pålsson 2011-05-02 16:45:13 +02:00
commit 816788c03d
1 changed files with 38 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

38
report.lyx
View file

@ -3311,6 +3311,28 @@ name "sec:Communication-with-external"
\end_inset
\end_layout
\begin_layout Standard
A game launched on the GGS is run with help of a virtual machine.
For each programming language supported, there is a virtual machine that
interprets it and an interface for communication between the GGS, the game
and the players playing the game.
Callbacks written in Erlang are registered to the vm for the interface
to work.
It is only with the help of the interface that the game developer can access
the game state and share data between players.
The interface provides access to three objects called World, Player and
Localstorage.
The game state is safely stored in a database and retrieved for manipulation
by a call for the World object.
Interaction with the players is done the same way using the Player object
instead.
The Localstorage is a convenient way to store globals and other variables
seperated from the game state.
Unique id:s called gametokens are generated for hosted games so that they
are not mixed up.
\end_layout
\begin_layout Standard
@ -3358,7 +3380,7 @@ name "sec:The-modular-structure"
\begin_layout Standard
The separation of concerns, and principle of single responsibility
\begin_inset Foot
status collapsed
status open
\begin_layout Plain Layout
More information on the SRP is available at:
@ -3998,6 +4020,20 @@ After a crash in a table process, the entire table must be rebuilt and the
The game virtual machine module
\end_layout
\begin_layout Standard
This module is holds the game logic of a game and is responsible for the
vm associated with each game.
It consists the state of the vm and a table token associated with a running
game.
The game token is given to game vm during initialization.
This will create a new vm instance and various objects associated to the
vm instance.
Then the source code of a game is loaded into the vm and the game is ready
for startup.
This module does not affect game runtime but evaluates a new game state
and handles communication between the game and the players.
\end_layout
\begin_layout Subsection
The database module
\begin_inset CommandInset label