minor changes to the language
This commit is contained in:
parent
1aac03c7eb
commit
926049ca06
1 changed files with 17 additions and 13 deletions
30
report.lyx
30
report.lyx
|
@ -7289,7 +7289,9 @@ This chapter contains descriptions of specific problems encountered when
|
||||||
|
|
||||||
\begin_layout Standard
|
\begin_layout Standard
|
||||||
The integration of JavaScript as a GDL in the GGS prototype was particularly
|
The integration of JavaScript as a GDL in the GGS prototype was particularly
|
||||||
difficult, and is handled in this section, so is the protocol design.
|
difficult, and is handled in this section, so is the protocol design and
|
||||||
|
limitation in the operating systems which have been used during the development
|
||||||
|
and tests.
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Section
|
\begin_layout Section
|
||||||
|
@ -7319,7 +7321,7 @@ and
|
||||||
\emph on
|
\emph on
|
||||||
IonMonkey
|
IonMonkey
|
||||||
\emph default
|
\emph default
|
||||||
, and also there is Googles
|
, and also there is Google's
|
||||||
\emph on
|
\emph on
|
||||||
V8
|
V8
|
||||||
\emph default
|
\emph default
|
||||||
|
@ -7367,14 +7369,15 @@ erlv8
|
||||||
\begin_layout Standard
|
\begin_layout Standard
|
||||||
erlv8 is powered by the V8 engine developed by Google.
|
erlv8 is powered by the V8 engine developed by Google.
|
||||||
The ability to communicate from JavaScript to Erlang using NIF callbacks
|
The ability to communicate from JavaScript to Erlang using NIF callbacks
|
||||||
is available in the erlv8 bindings and can be used within the GGS.
|
is is present in the erlv8 bindings and can be used within the GGS.
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Standard
|
\begin_layout Standard
|
||||||
Initial releases of the erlv8 bindings had stability issues, these however
|
Initial releases of the erlv8 bindings had stability issues, these however
|
||||||
were resolved by the erlv8 developers during the development GGS.
|
were resolved by the erlv8 developers during the development GGS.
|
||||||
At this point erlv8 is the JavaScript engine powering JavaScript as a GDL
|
While still described to be in 'alpha' stage, the erlv8 bindings have proved
|
||||||
in the GGS.
|
to be stable nough and at this point erlv8 is the JavaScript engine powering
|
||||||
|
JavaScript as a GDL in the GGS.
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Standard
|
\begin_layout Standard
|
||||||
|
@ -7409,7 +7412,8 @@ Protocol design
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Standard
|
\begin_layout Standard
|
||||||
Initially the GGS protocol was planed to use the UDP protocol for transport.
|
Initially the GGS protocol was planed to use the UDP protocol as a transport
|
||||||
|
layer.
|
||||||
Due to the lack of error checking in the UDP protocol, the UDP protocol
|
Due to the lack of error checking in the UDP protocol, the UDP protocol
|
||||||
is faster than the TCP protocol, this was a main reason in the desire to
|
is faster than the TCP protocol, this was a main reason in the desire to
|
||||||
use UDP.
|
use UDP.
|
||||||
|
@ -7439,16 +7443,16 @@ key "Slee2007"
|
||||||
Using Thrift would mean the GGS would feature a standard protocol for network
|
Using Thrift would mean the GGS would feature a standard protocol for network
|
||||||
communication.
|
communication.
|
||||||
Before finding out about Thrift during a lecture of Joe Armstrong (one
|
Before finding out about Thrift during a lecture of Joe Armstrong (one
|
||||||
of the inventors of Erlang), an implementation of the GGS protocol had
|
of the inventors of Erlang), the GGS protocol had already been implemented,
|
||||||
already been implemented, moving to Thrift would mean too much efford for
|
moving to Thrift would have meant too much efford for a prototype during
|
||||||
a prototype during the short amount of time.
|
the short amount of time.
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Standard
|
\begin_layout Standard
|
||||||
The use of Google protocol buffers - which is a different approach to a
|
The use of Google protocol buffers - which is a different approach to a
|
||||||
standard protocol framework, implemented by Google - or other protocols
|
standard protocol framework, implemented by Google - or other protocols
|
||||||
can be supported quite easily by developing protocol modules for each the
|
can be supported quite easily by developing protocol modules for each of
|
||||||
protocols.
|
the protocols.
|
||||||
No protocol modules for these protocols have however been developed during
|
No protocol modules for these protocols have however been developed during
|
||||||
the writing of this thesis.
|
the writing of this thesis.
|
||||||
\end_layout
|
\end_layout
|
||||||
|
@ -7465,8 +7469,8 @@ name "sec:Operating-system-limitations"
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
||||||
\begin_layout Standard
|
\begin_layout Standard
|
||||||
The operating systems on the computers which were used to run the bots when
|
The operating systems on the computers which have been used to run the bots
|
||||||
testing the GGS prototype had some limitations.
|
while testing the GGS prototype had some limitations.
|
||||||
The operating systems used were Linux and Mac OS X, since these systems
|
The operating systems used were Linux and Mac OS X, since these systems
|
||||||
are quite similar on a lower level they exhibited the same limitations..
|
are quite similar on a lower level they exhibited the same limitations..
|
||||||
\end_layout
|
\end_layout
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue