Merge branch 'master' of github.com:jeena/GGS-report
This commit is contained in:
commit
dcd8660b9d
1 changed files with 14 additions and 11 deletions
25
report.lyx
25
report.lyx
|
@ -7326,15 +7326,15 @@ name "cha:Problems-of-implementation"
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This chapter contains specific problems encountered when implementing the
|
||||
GGS prototype.
|
||||
This chapter contains descriptions of specific problems encountered when
|
||||
implementing the GGS prototype.
|
||||
Some of the problems described have solutions attached, however some problems
|
||||
were not solved, therefore only ideas for solutions have been attached.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The integration of JavaScript as a GDL in the GGS prototype was particularly
|
||||
difficult, and is handled in this section and so is the protocol design.
|
||||
difficult, and is handled in this section, so is the protocol design.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
|
@ -7376,6 +7376,8 @@ V8
|
|||
\begin_layout Standard
|
||||
For the Mozilla machines, there exists a Erlang binding called erlang_js,
|
||||
and for the V8 machine a binding called erlv8 exists.
|
||||
Below follows a discussion about the different bindings and machines, and
|
||||
a motivation as to why erlv8 was preferred over erlang_js.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
|
@ -7383,9 +7385,9 @@ erlang_js
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
erlang_js provides direct communication with the JavaScript VM.
|
||||
Which is exactly what is desired, however also required is the possibility
|
||||
to communicate from JavaScript to Erlang.
|
||||
erlang_js provides direct communication with the JavaScript VM, which is
|
||||
exactly what is desired, however also required is the possibility to communicat
|
||||
e from JavaScript to Erlang.
|
||||
The ability to communicate from JavaScript to Erlang is not yet implemented
|
||||
in erlang_js, due to lack of time of the erlang_js developers.
|
||||
\end_layout
|
||||
|
@ -7409,8 +7411,8 @@ erlv8
|
|||
|
||||
\begin_layout Standard
|
||||
erlv8 is powered by the V8 engine developed by Google.
|
||||
The ability to communicate from JavaScript to Erlang using callbacks (aka
|
||||
NIF) is available in the erlv8 bindings and can be used within the GGS.
|
||||
The ability to communicate from JavaScript to Erlang using NIF callbacks
|
||||
is available in the erlv8 bindings and can be used within the GGS.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
@ -7488,9 +7490,10 @@ key "Slee2007"
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The use of Thrift, Google protocol buffers - which is a different approach
|
||||
to that implemented by Google - or other protocols can be supported quite
|
||||
easily by developing protocol modules for each the protocols.
|
||||
The use of Google protocol buffers - which is a different approach to a
|
||||
standard protocol framework, implemented by Google - or other protocols
|
||||
can be supported quite easily by developing protocol modules for each the
|
||||
protocols.
|
||||
No protocol modules for these protocols have however been developed during
|
||||
the writing of this thesis.
|
||||
\end_layout
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue