From acb91e5e225d51734e276da3c96733bb2a426aec Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 22:36:15 +0200 Subject: [PATCH 1/5] Revised chapter 4 intro --- report.lyx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/report.lyx b/report.lyx index 501f8a4..ddb4650 100644 --- a/report.lyx +++ b/report.lyx @@ -7327,15 +7327,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 From b99f00dc3c7537433e2e3393c0c52195e6adae34 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 22:37:49 +0200 Subject: [PATCH 2/5] Revised 4.1 --- report.lyx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/report.lyx b/report.lyx index ddb4650..33981ab 100644 --- a/report.lyx +++ b/report.lyx @@ -7377,6 +7377,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 From d99f76b644447709cc82027521ca4bea10027600 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 22:38:35 +0200 Subject: [PATCH 3/5] Revised 4.1.1 --- report.lyx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/report.lyx b/report.lyx index 33981ab..e80bc14 100644 --- a/report.lyx +++ b/report.lyx @@ -7386,9 +7386,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 From 95b12005a50e5e9da270eda5a86763e50ac116de Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 22:39:34 +0200 Subject: [PATCH 4/5] Revised 4.1.2 --- report.lyx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/report.lyx b/report.lyx index e80bc14..4adfd5f 100644 --- a/report.lyx +++ b/report.lyx @@ -7412,8 +7412,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 From e3fa7a50164d3113dcad8dc88b47c17e4b6735b5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonatan=20P=C3=A5lsson?= Date: Thu, 12 May 2011 22:41:40 +0200 Subject: [PATCH 5/5] Revised 4.2 --- report.lyx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/report.lyx b/report.lyx index 4adfd5f..9fd5831 100644 --- a/report.lyx +++ b/report.lyx @@ -7491,9 +7491,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