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

Moved JS code back in, and changed the first case study some

Browse source
This commit is contained in:
Jonatan Pålsson 2011-05-10 11:33:33 +02:00
parent c4cdcb099d
commit 775ea8567c
1 changed files with 9 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

17
report.lyx
View file

@ -6558,9 +6558,10 @@ Typical communication
\end_layout \end_layout
\begin_layout Standard \begin_layout Standard
So what happens when a client sends a typical game command? Let us look This case study describes the flow through the GGS when a typical command
at one particular example of a chat client sending the message to change is encountered.
the nick of a user (we will discuss a example implementation in JavaScript Consider a chat client sending the message to change the nick of a user.
The actual code performing the change of a nick in JavaScript is discussed
in section in section
\begin_inset CommandInset ref \begin_inset CommandInset ref
LatexCommand ref LatexCommand ref
@ -6568,9 +6569,9 @@ reference "sec:Example-of-a-GGS-app"
\end_inset \end_inset
). .
Every communication between modules happens asynchronously, nothing is All communication between modules is asynchronous, nothing is blocking,
blocking, which is very important in concurrent systems. which is very important in concurrent systems.
It is probably much easier to follow the steps by following them on It is probably much easier to follow the steps by following them on
\begin_inset CommandInset ref \begin_inset CommandInset ref
LatexCommand vref LatexCommand vref
@ -6721,8 +6722,8 @@ Fill this in!
\end_layout \end_layout
\begin_layout Section \begin_layout Subsection
Example of a GGS server application in JavaScript A GGS server application in JavaScript
\begin_inset CommandInset label \begin_inset CommandInset label
LatexCommand label LatexCommand label
name "sec:Example-of-a-GGS-app" name "sec:Example-of-a-GGS-app"