- About
-
The Global ETD Search service is a free service for researchers
to find electronic theses and dissertations. This service is
provided by the
Networked Digital Library of Theses and Dissertations.
Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
Search results
Showing 121 to 129 of 129 (0.018 seconds)| 121 |
Garbage Collected CRDTs on the Web : Studying the Memory Efficiency of CRDTs in a Web ContextRehn, Michael January 2020 (has links)
In today's connected society, where it is common to have several connected devices per capita, it is more important than ever that the data you need is omnipresent, i.e. its available when you need it, no matter where you are. We identify one key technology and platform that could be the future—peer-to-peer communication and the Web. Unfortunately, guaranteeing consistency and availability between users in a peer-to-peer network, where network partitions are bound to happen, can be a challenging problem to solve. To solve these problems, we turned to a promising category of data types called CRDTs—Conflict Free Replicated Data Types. By following the scientific tradition of reproduction, we build upon previous research of a CRDT framework, and adjust it work in a peer-to-peer Web environment, i.e. it runs on a Web browser. CRDTs makes use of meta-data to ensure consistency, and it is imperative to remove this meta-data once it no longer has any use—if not, memory usage grows unboundedly making the CRDT impractical for real-world use. There are different garbage collection techniques that can be applied to remove this meta-data. To investigate whether the CRDT framework and the different garbage collection techniques are suitable for the Web, we try to reproduce previous findings by running our implementation through a series of benchmarks. We test whether our implementation works correctly on the Web, as well as comparing the memory efficiency between different garbage collection techniques. In doing this, we also proved the correctness of one of these techniques. The results from our experiments showed that the CRDT framework was well-adjusted to the Web environment and worked correctly. However, while we could observe similar behaviour between different garbage collection techniques as previous research, we achieved lower relative memory savings than expected. An additional insight was that for long-running systems that often reset its shared state, it might be more efficient to not apply any garbage collection technique at all. There is still much work to be done to allow for omnipresent data on the Web, but we believe that this research contains two main takeaways. The first is that the general CRDT framework is well-suited for the Web and that it in practice might be more efficient to choose different garbage collection techniques, depending on your use-case. The second take-away is that by reproducing previous research, we can still advance the current state of the field and generate novel knowledge—indeed, by combining previous ideas in a novel environment, we are now one step closer to a future with omnipresent data. / I dagens samhälle är vi mer uppkopplade än någonsin. Tack vare det faktum att vi nu ofta har fler än en uppkopplad enhet per person, så är det viktigare än någonsin att ens data är tillgänglig på alla ens enheter–oavsett vart en befinner sig. Två tekniker som kan möjliggöra denna ``allnärvaro'' av data är Webben, alltså kod som körs på en Webbläsare, tillsammans med peer-to-peer-kommunikation; men att säkerställa att distribuerad data både är tillgänglig och likadan för alla enheter är svårt, speciellt när enhetens internetanslutning kan brytas när som helst. Conflict-free replicated data-types (CRDT:er) är en lovande klass av datatyper som löser just dessa typer av problem i distribuerade system; genom att använda sig av meta-data, så kan CRDT:er fortsätta fungera trots att internetanslutningen brutits. Dessutom är de garanterade att konvergera till samma sluttillstånd när anslutningen upprättas igen. Däremot lider CRDT:er av ett speciellt problem–denna meta-data tar upp mycket minne trots att den inte har någon användning efter en stund. För att göra datatypen mer minneseffektiv så kan meta-datan rensas bort i en process som kallas för skräpsamling. Vår idé var därför att reproducera tidigare forskning om ett ramverk för CRDT:er och försöka anpassa denna till att fungera på Webben. Vi reproducerar dessutom olika metoder för skräpsamling för att undersöka om de, för det första fungerar på Webben, och för det andra är lika effektiv i denna nya miljö som den tidigare forskningen pekar på. Resultaten från våra experiment visade att CRDT-ramverket och dess olika skräpsamlingsmetoder kunde anpassas till att fungera på Webben. Däremot så noterade vi något högre relativ minnesanvändning än vad vi har förväntat oss, trots att beteendet i stort var detsamma som den tidigare forskningen. En ytterligare upptäckt vad att i vissa specifika fall så kan det vara mer effektivt att inte applicera någon skräpsamling alls. Trots att det är mycket arbete kvar för att använder CRDT:er peer-to-peer på Webben för att möjliggöra ``allnärvarande'' data, så innehåller denna uppsats två huvudsakliga punkter. För det första så fungerar det att anpassa CRDT-ramverket och dess olika skräpsamlingsmetoder till Webben, men ibland är det faktiskt bättre att inte applicera någon skräpsamling alls. För det andra så visas vikten av att reproducera tidigare forskning–inte bara visar uppsatsen att tidigare CRDT-forskning kan appliceras i andra miljöer, dessutom kan ny kunskap hämtas ur en sådan reproducering.
|
| 122 |
Swedes Online: You Are More Tracked Than You ThinkPurra, Joel January 2015 (has links)
When you are browsing websites, third-party resources record your online habits; such tracking can be considered an invasion of privacy. It was previously unknown how many third-party resources, trackers and tracker companies are present in the different classes of websites chosen: globally popular websites, random samples of .se/.dk/.com/.net domains and curated lists of websites of public interest in Sweden. The in-browser HTTP/HTTPS traffic was recorded while downloading over 150,000 websites, allowing comparison of HTTPS adaption and third-party tracking within and across the different classes of websites. The data shows that known third-party resources including known trackers are present on over 90% of most classes, that third-party hosted content such as video, scripts and fonts make up a large portion of the known trackers seen on a typical website and that tracking is just as prevalent on secure as insecure sites. Observations include that Google is the most widespread tracker organization by far, that content is being served by known trackers may suggest that trackers are moving to providing services to the end user to avoid being blocked by privacy tools and ad blockers, and that the small difference in tracking between using HTTP and HTTPS connections may suggest that users are given a false sense of privacy when using HTTPS. / <p>Source code, datasets, and a video recording of the presentation is available on the master's thesis website.</p>
|
| 123 |
Visualisierung großer Datenmengen im Raum / Visualising Large Amounts of Data in 3D SpacePolowinski, Jan 09 April 2013 (has links) (PDF)
Large, strongly connected amounts of data, as collected in knowledge bases or those occurring when describing software, are often read slowly and with difficulty by humans when they are represented as spreadsheets or text. Graphical representations can help people to understand facts more intuitively and offer a quick overview. The electronic representation offers means that are beyond the possibilities of print such as unlimited zoom and hyperlinks.
This paper addresses a framework for visualizing connected information in 3D-space taking into account the techniques of media design to build visualization structures and map information to graphical properties. / Große, stark vernetzte Datenmengen, wie sie in Wissensbasen oder Softwaremodellen vorkommen, sind von Menschen oft nur langsam und mühsam zu lesen, wenn sie als Tabellen oder Text dargestellt werden. Graphische Darstellungen können Menschen helfen, Tatsachen intuitiver zu verstehen und bieten einen schnellen Überblick. Die elektronische Darstellung bietet Mittel, welche über die Möglichkeiten von Print hinausgehen, wie z.B. unbegrenzten Zoom und Hyperlinks.
Diese Arbeit stellt ein Framework für die Visualisierung vernetzter Informationen im 3D-Raum vor, welches Techniken der Gestaltung zur Erstellung von graphischen Strukturen und zur Abbildung von Informationen auf graphische Eigenschaften berücksichtigt.
|
| 124 |
Využití technologie Blazor s frameworkem DotVVM / Using Blazor technology with the DotVVM frameworkŠvikruha, Patrik January 2019 (has links)
DotVVM, WebAssembly, WASM, Blazor, ASP.NET Core, .NET Core, .NET, Mono, JavaScript, JavaScript engine, LLVM, AOT compiler, JIT compiler, WSL
|
| 125 |
Automatické testování projektu JavaScript Restrictor / Automatic Testing of JavaScript Restrictor ProjectBednář, Martin January 2020 (has links)
The aim of the thesis was to design, implement and evaluate the results of automatic tests for the JavaScript Restrictor project, which is being developed as a web browser extension. The tests are divided into three levels - unit, integration, and system. The Unit Tests verify the behavior of individual features, the Integration Tests verify the correct wrapping of browser API endpoints, and the System Tests check that the extension does not suppress the desired functionality of web pages. The System Tests are implemented for parallel execution in a distributed environment which has succeeded in achieving an almost directly proportional reduction in time with respect to the number of the tested nodes. The benefit of this work is detection of previously unknown errors in the JavaScript Restrictor extension and provision of the necessary information that allowed to fix some of the detected bugs.
|
| 126 |
Správa vývojové dokumentace přes WWW II / Administration of development documetation over WWW IIGregárek, Ondřej January 2008 (has links)
Document server is a web application controllable by way of web browser. It is meant to serve for the management of development documentation. The application is divided to the four basic parts: Requirements, Products, Tests and Test Run. The section Requirements serves for inserting requirements for products. Product is produced on the basis of these needs and registered in part Products. Test setting is created in the part Tests according to requirements from the part Requirements. Particular products are then tested. The part Test Run registers records of these tests. These are parts of the application: management of users, connecting supplements to records, printing and exportation of data to different formats, saving history of records, filtration and sorting of entries, etc. All the data is saved in the database MySQL. The application is written in scripting language PHP. Data is presented by template system Smarty. The output is in language XHTML. Cascading style CSS is used to formatting. This work describes development of the application. First it is dealing with the proposal of the database, connection and structure of particular tables. The function of the programme is explained in detail at the same time, which is essential for the correct proposal of the database. The application is based on the database. The selected structure of files and relations of scripts to library functions are shown. The template system and the interface for access of the programme to the database are explained. The most attention is paid to the description of solving important functions of the application, i.e. listing of records, their pagination, filtration, sorting and operation with them: saving, browsing, copying, confirmation and work with history, category and problems by upkeep of consistent tree and export of data to various formats. It is always outlined the problem, the idea of solving and the description of appropriate scripts. Samples of source code are also included for better understanding of complicated algorithms.
|
| 127 |
Visualisierung großer Datenmengen im Raum: Großer BelegPolowinski, Jan 14 June 2006 (has links)
Large, strongly connected amounts of data, as collected in knowledge bases or those occurring when describing software, are often read slowly and with difficulty by humans when they are represented as spreadsheets or text. Graphical representations can help people to understand facts more intuitively and offer a quick overview. The electronic representation offers means that are beyond the possibilities of print such as unlimited zoom and hyperlinks.
This paper addresses a framework for visualizing connected information in 3D-space taking into account the techniques of media design to build visualization structures and map information to graphical properties.:1 EINFÜHRUNG S. 9
1.1 Zusammenfassung des Gestaltungsentwurfs S. 9
1.2 Ziel des Belegs S. 10
1.3 Interdisziplinäres Projekt S. 10
2 VORGEHEN S. 12
2.1 Ablauf S. 12
2.2 Konkrete Beispielinhalte S. 13
2.3 Beispielimplementierung S. 13
3 DATENMODELL S. 15
3.1 Ontologien S. 15
3.2 Ontologie Konstruktion S. 15
3.3 Analyse der Domain Design S. 18
3.8 Erstes Ordnen S. 19
3.9 Verwendete Ontologie-Struktur S. 21
3.10 Design-Ontologien S. 23
3.11 Schwierigkeiten bei der Ontologiekonstruktion S. 28
3.12 Einpflegen der Daten mit Protégé S. 29
3.13 Facetten S. 29
3.14 Filter S. 32
4 DATENVISUALISIERUNG S. 35
4.1 Visualisierung zeitlicher Daten S. 35
4.2 Hyperhistory S. 35
4.3 Graphisches Vokabular - graphische Dimensionen S. 37
4.4 Mapping S. 39
5 FRAMEWORK UND GESTALTUNG DES MEDIUMS S. 43
5.1 Technologien und Werkzeuge S. 44
5.2 Architektur S. 46
5.3 Konfiguration S. 51
5.4 DataBackendManager S. 52
5.5 Mapping im Framework S. 53
5.6 atomicelements S. 54
5.7 Appearance Bibliothek S. 55
5.8 TransformationUtils S. 56
5.9 Structures S. 57
5.10 LOD S. 64
5.11 Häufung von Einträgen [+] S. 66
5.12 Darstellung von Relationen [+] S. 69
5.13 Head Up Display [+] S. 71
5.14 Navigation S. 72
5.15 Performanz S. 73
5.16 Gestaltung des Mediums S. 74
6 AUSBLICK S. 80
7 FAZIT S. 81
8 ANHANG A – Installation S. 82
8.1 Vorraussetzungen S. 82
8.2 Programmaufruf S. 82
8.3 Stereoskopie S. 82
9 ANHANG B – Beispielimplementierung zur Visualisierung des Themas „Geschichte des Designs in Deutschland im 19. und 20. Jh.“ S. 84
9.1 Eingrenzung des Umfangs S. 84
9.2 Überblick zur deutschen Designgeschichte S. 84
9.3 Vorgehen S. 85
9.4 Unscharfe Datumsangaben S. 85
9.5 Kontextereignisse S. 85
9.6 Ursache-Wirkung-Beziehungen S. 86
9.7 Mehrsprachigkeit S. 86
9.8 Quellenangaben S. 86
9.9 Bildmaterial S. 87
LITERATURVERZEICHNIS S. 88
GLOSSAR S. 90
ABBILDUNGSVERZEICHNIS S. 91 / Große, stark vernetzte Datenmengen, wie sie in Wissensbasen oder Softwaremodellen vorkommen, sind von Menschen oft nur langsam und mühsam zu lesen, wenn sie als Tabellen oder Text dargestellt werden. Graphische Darstellungen können Menschen helfen, Tatsachen intuitiver zu verstehen und bieten einen schnellen Überblick. Die elektronische Darstellung bietet Mittel, welche über die Möglichkeiten von Print hinausgehen, wie z.B. unbegrenzten Zoom und Hyperlinks.
Diese Arbeit stellt ein Framework für die Visualisierung vernetzter Informationen im 3D-Raum vor, welches Techniken der Gestaltung zur Erstellung von graphischen Strukturen und zur Abbildung von Informationen auf graphische Eigenschaften berücksichtigt.:1 EINFÜHRUNG S. 9
1.1 Zusammenfassung des Gestaltungsentwurfs S. 9
1.2 Ziel des Belegs S. 10
1.3 Interdisziplinäres Projekt S. 10
2 VORGEHEN S. 12
2.1 Ablauf S. 12
2.2 Konkrete Beispielinhalte S. 13
2.3 Beispielimplementierung S. 13
3 DATENMODELL S. 15
3.1 Ontologien S. 15
3.2 Ontologie Konstruktion S. 15
3.3 Analyse der Domain Design S. 18
3.8 Erstes Ordnen S. 19
3.9 Verwendete Ontologie-Struktur S. 21
3.10 Design-Ontologien S. 23
3.11 Schwierigkeiten bei der Ontologiekonstruktion S. 28
3.12 Einpflegen der Daten mit Protégé S. 29
3.13 Facetten S. 29
3.14 Filter S. 32
4 DATENVISUALISIERUNG S. 35
4.1 Visualisierung zeitlicher Daten S. 35
4.2 Hyperhistory S. 35
4.3 Graphisches Vokabular - graphische Dimensionen S. 37
4.4 Mapping S. 39
5 FRAMEWORK UND GESTALTUNG DES MEDIUMS S. 43
5.1 Technologien und Werkzeuge S. 44
5.2 Architektur S. 46
5.3 Konfiguration S. 51
5.4 DataBackendManager S. 52
5.5 Mapping im Framework S. 53
5.6 atomicelements S. 54
5.7 Appearance Bibliothek S. 55
5.8 TransformationUtils S. 56
5.9 Structures S. 57
5.10 LOD S. 64
5.11 Häufung von Einträgen [+] S. 66
5.12 Darstellung von Relationen [+] S. 69
5.13 Head Up Display [+] S. 71
5.14 Navigation S. 72
5.15 Performanz S. 73
5.16 Gestaltung des Mediums S. 74
6 AUSBLICK S. 80
7 FAZIT S. 81
8 ANHANG A – Installation S. 82
8.1 Vorraussetzungen S. 82
8.2 Programmaufruf S. 82
8.3 Stereoskopie S. 82
9 ANHANG B – Beispielimplementierung zur Visualisierung des Themas „Geschichte des Designs in Deutschland im 19. und 20. Jh.“ S. 84
9.1 Eingrenzung des Umfangs S. 84
9.2 Überblick zur deutschen Designgeschichte S. 84
9.3 Vorgehen S. 85
9.4 Unscharfe Datumsangaben S. 85
9.5 Kontextereignisse S. 85
9.6 Ursache-Wirkung-Beziehungen S. 86
9.7 Mehrsprachigkeit S. 86
9.8 Quellenangaben S. 86
9.9 Bildmaterial S. 87
LITERATURVERZEICHNIS S. 88
GLOSSAR S. 90
ABBILDUNGSVERZEICHNIS S. 91
|
| 128 |
Web applications using the Google Web Toolkit / Webanwendungen unter Verwendung des Google Web Toolkitsvon Wenckstern, Michael 04 June 2013 (has links) (PDF)
This diploma thesis describes how to create or convert traditional Java programs to desktop-like rich internet applications with the Google Web Toolkit.
The Google Web Toolkit is an open source development environment, which translates Java code to browser and device independent HTML and JavaScript.
Most of the GWT framework parts, including the Java to JavaScript compiler as well as important security issues of websites will be introduced.
The famous Agricola board game will be implemented in the Model-View-Presenter pattern to show that complex user interfaces can be created with the Google Web Toolkit.
The Google Web Toolkit framework will be compared with the JavaServer Faces one to find out which toolkit is the right one for the next web project. / Diese Diplomarbeit beschreibt die Erzeugung desktopähnlicher Anwendungen mit dem Google Web Toolkit und die Umwandlung klassischer Java-Programme in diese.
Das Google Web Toolkit ist eine Open-Source-Entwicklungsumgebung, die Java-Code in browserunabhängiges als auch in geräteübergreifendes HTML und JavaScript übersetzt.
Vorgestellt wird der Großteil des GWT Frameworks inklusive des Java zu JavaScript-Compilers sowie wichtige Sicherheitsaspekte von Internetseiten.
Um zu zeigen, dass auch komplizierte graphische Oberflächen mit dem Google Web Toolkit erzeugt werden können, wird das bekannte Brettspiel Agricola mittels Model-View-Presenter Designmuster implementiert.
Zur Ermittlung der richtigen Technologie für das nächste Webprojekt findet ein Vergleich zwischen dem Google Web Toolkit und JavaServer Faces statt.
|
| 129 |
Web applications using the Google Web Toolkitvon Wenckstern, Michael 05 June 2013 (has links)
This diploma thesis describes how to create or convert traditional Java programs to desktop-like rich internet applications with the Google Web Toolkit.
The Google Web Toolkit is an open source development environment, which translates Java code to browser and device independent HTML and JavaScript.
Most of the GWT framework parts, including the Java to JavaScript compiler as well as important security issues of websites will be introduced.
The famous Agricola board game will be implemented in the Model-View-Presenter pattern to show that complex user interfaces can be created with the Google Web Toolkit.
The Google Web Toolkit framework will be compared with the JavaServer Faces one to find out which toolkit is the right one for the next web project.:I Abstract
II Contents
III Acronyms and Glossary
III.I Acronyms
III.II Glossary
IV Credits
1 Introduction
2 Basics
2.1 Development of the World Wide Web
2.2 Hypertext Markup Language
2.3 Cascading Style Sheets
2.4 JavaScript
2.5 Hypertext Markup Language Document Object Model
2.6 Asynchronous JavaScript and XML
3 GWT toolbox and compiler
3.1 GWT in action
3.2 A short overview of the toolkit
3.3 GWT compiler and JSNI
3.3.1 Overview of GWT compiler and JSNI
3.3.2 Deferred binding and bootstrapping process
3.3.3 GWT compiler steps and optimizations
3.4 Java Runtime Environment Emulation
3.5 Widgets and Panels
3.5.1 Overview of GWT Widgets
3.5.2 Event handlers in GWT Widgets
3.5.3 Manipulating browser’s DOM with GWT DOM class
3.5.4 GWT Designer and view optimization using UiBinder
3.6 Remote Procedure Calls
3.6.1 Comparison of Remote Procedure Calls with Remote Method Invocations
3.6.2 GWT’s RPC service and serializable whitelist
3.7 History Management
3.8 Client Bundle
3.8.1 Using ImageResources in the ClientBundle interface
3.8.2 Using CssResources in the ClientBundle interface
4 Model-View-Presenter Architecture
4.1 Comparison of MVP and MVC
4.2 GWT Model-View-Presenter pattern example: Agricola board game
4.3 Extending the Agricola web application with mobile views
4.4 Introducing activities in the Agricola Model-View-Presenter pattern enabling browser history
5 Comparison of the two web frameworks: GWT and JSF
5.1 Definitions of comparison fields
5.2 Comparison in category 1: Nearly completely static sites with a little bit of dynamic content, e.g. news update
5.3 Comparison in category 2: Doing a survey in both technologies
5.4 Comparison in category 3: Creating a forum to show data
5.5 Comparison in category 4: Writing a chat application
5.6 Comparison in category 5: Writing the speed game Snake
5.7 Summary
6 Security
6.1 Download Tomcat
6.2 Dynamic Web Application Project with GWT and Tomcat
6.3 Establish HTTPS connections in Tomcat
6.3.1 Create a pem certificate
6.3.2 Convert pem certificate into a key store object
6.3.3 Configure Tomcat’s XML files to enable HTPPS
6.4 Establish a database connection in Tomcat
6.4.1 Create TomcatGWT user and schema, and add the table countries
6.4.2 Configure Tomcat’s XML files to get access to the database connection
6.4.3 PreparedStatements avoid MySQL injections
6.5 Login mechanism in Tomcat
6.6 SafeHtml
7 Presenting a complex software application written in GWT
8 Conclusions
8.1 Summary
8.2 Future work
A Appendix
A 1 Configure the Google Web Toolkit framework in Eclipse
A 1.1 Install the Java Developer Kit
A 1.2 Download Eclipse
A 1.3 Install the GWT plugin in Eclipse
A 1.4 Create first GWT Java Project
A 2 Figures
A 3 Listings
A 3.1 Source code of the Agricola board game
A 3.2 Source code of GWT and JSF comparison
A 4 Tables
R Lists and References
R 1 Lists
R 1.1 List of Tables
R 1.2 List of Figures
R 1.3 List of Listings
R 2 References
R 2.1 Books
R 2.2 Online resources / Diese Diplomarbeit beschreibt die Erzeugung desktopähnlicher Anwendungen mit dem Google Web Toolkit und die Umwandlung klassischer Java-Programme in diese.
Das Google Web Toolkit ist eine Open-Source-Entwicklungsumgebung, die Java-Code in browserunabhängiges als auch in geräteübergreifendes HTML und JavaScript übersetzt.
Vorgestellt wird der Großteil des GWT Frameworks inklusive des Java zu JavaScript-Compilers sowie wichtige Sicherheitsaspekte von Internetseiten.
Um zu zeigen, dass auch komplizierte graphische Oberflächen mit dem Google Web Toolkit erzeugt werden können, wird das bekannte Brettspiel Agricola mittels Model-View-Presenter Designmuster implementiert.
Zur Ermittlung der richtigen Technologie für das nächste Webprojekt findet ein Vergleich zwischen dem Google Web Toolkit und JavaServer Faces statt.:I Abstract
II Contents
III Acronyms and Glossary
III.I Acronyms
III.II Glossary
IV Credits
1 Introduction
2 Basics
2.1 Development of the World Wide Web
2.2 Hypertext Markup Language
2.3 Cascading Style Sheets
2.4 JavaScript
2.5 Hypertext Markup Language Document Object Model
2.6 Asynchronous JavaScript and XML
3 GWT toolbox and compiler
3.1 GWT in action
3.2 A short overview of the toolkit
3.3 GWT compiler and JSNI
3.3.1 Overview of GWT compiler and JSNI
3.3.2 Deferred binding and bootstrapping process
3.3.3 GWT compiler steps and optimizations
3.4 Java Runtime Environment Emulation
3.5 Widgets and Panels
3.5.1 Overview of GWT Widgets
3.5.2 Event handlers in GWT Widgets
3.5.3 Manipulating browser’s DOM with GWT DOM class
3.5.4 GWT Designer and view optimization using UiBinder
3.6 Remote Procedure Calls
3.6.1 Comparison of Remote Procedure Calls with Remote Method Invocations
3.6.2 GWT’s RPC service and serializable whitelist
3.7 History Management
3.8 Client Bundle
3.8.1 Using ImageResources in the ClientBundle interface
3.8.2 Using CssResources in the ClientBundle interface
4 Model-View-Presenter Architecture
4.1 Comparison of MVP and MVC
4.2 GWT Model-View-Presenter pattern example: Agricola board game
4.3 Extending the Agricola web application with mobile views
4.4 Introducing activities in the Agricola Model-View-Presenter pattern enabling browser history
5 Comparison of the two web frameworks: GWT and JSF
5.1 Definitions of comparison fields
5.2 Comparison in category 1: Nearly completely static sites with a little bit of dynamic content, e.g. news update
5.3 Comparison in category 2: Doing a survey in both technologies
5.4 Comparison in category 3: Creating a forum to show data
5.5 Comparison in category 4: Writing a chat application
5.6 Comparison in category 5: Writing the speed game Snake
5.7 Summary
6 Security
6.1 Download Tomcat
6.2 Dynamic Web Application Project with GWT and Tomcat
6.3 Establish HTTPS connections in Tomcat
6.3.1 Create a pem certificate
6.3.2 Convert pem certificate into a key store object
6.3.3 Configure Tomcat’s XML files to enable HTPPS
6.4 Establish a database connection in Tomcat
6.4.1 Create TomcatGWT user and schema, and add the table countries
6.4.2 Configure Tomcat’s XML files to get access to the database connection
6.4.3 PreparedStatements avoid MySQL injections
6.5 Login mechanism in Tomcat
6.6 SafeHtml
7 Presenting a complex software application written in GWT
8 Conclusions
8.1 Summary
8.2 Future work
A Appendix
A 1 Configure the Google Web Toolkit framework in Eclipse
A 1.1 Install the Java Developer Kit
A 1.2 Download Eclipse
A 1.3 Install the GWT plugin in Eclipse
A 1.4 Create first GWT Java Project
A 2 Figures
A 3 Listings
A 3.1 Source code of the Agricola board game
A 3.2 Source code of GWT and JSF comparison
A 4 Tables
R Lists and References
R 1 Lists
R 1.1 List of Tables
R 1.2 List of Figures
R 1.3 List of Listings
R 2 References
R 2.1 Books
R 2.2 Online resources
|
Page generated in 0.0273 seconds