- 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 1 to 6 of 6 (0.108 seconds)Spelling suggestions: "subject:"remote a'method invocation"" "subject:"remote a'method nvocation""
| 1 |
High level abstractions and visualization of sensor network applicationsPulluri, Sandeep January 1900 (has links)
Master of Science / Department of Computing and Information Sciences / Gurdip Singh / TinyOS is a component based operating system written in nesC programming language. TinyOS provides interfaces and components for common low level abstractions such as packet communication, routing and sensing for node level sensor network application programming. This project aims to provide high level abstractions to users by providing the notion of a virtual node, which represents a set of physical nodes, allowing users to specify global scenarios, and a mechanism to decompose a high level global scenario into local node level scenarios for each of the individual sensor nodes. A global scenario with virtual components, provided by the user, is first converted into a global scenario by eliminating the virtual components from the model by using a mapping information provided the user and replacing these virtual components by their respective physical components. Appropriate algorithm components and the automatically generated adapter components for these algorithm components are then plugged-in to implement inter-node interactions. This global scenario is then converted to the node level local scenarios by introducing the automatically generated proxy components for the remote components and connecting these proxy components using the RMI layer. The Cadena model is modified to include the attribute location for the components to identify the remote components. The make files are then generated for these local scenarios and are ready to be deployed on the physical motes.
The framework provides a GUI tool which is used to visualize the data of the sensor network in both simulation and deployment. The framework provides the user with commands that can be issued to the network from the Cadena component model as a set of interfaces to the components and a python script is used to capture this information in an xml file. The Cadena model is modified to include the attribute observable to the interfaces to identify them as the GUI commands. The GUI loads this XML file and the topology file for the actual deployment, can issue commands to the network and displays the results to the user. The GUI tool also enhances the Tossim simulator to model the external effects over the sensor network and to place the motes based on the topology information using the Tython environment.
|
| 2 |
Remote Method Invocation for Android Platform / Remote Method Invocation for Android PlatformMagic, Ľuboš January 2012 (has links)
The thesis inquires the potential of a remote method invocation in the context of the Android mobile devices. The primary goal of the thesis is to investigate execution of security-critical parts of application code on smart cards (a prominent example of a smart card is the SIM card). Further, the thesis discusses issues of implementation of the remote method invocation in general, covering also its other frequent forms (such as execution on a remote server). A part of the thesis is a real world case study, which demonstrates the results of the thesis.
|
| 3 |
Universal Mobile Service Execution Framework for Device-To-Device CollaborationsLe, Minh 01 May 2018 (has links)
There are high demands of effective and high-performance of collaborations between mobile devices in the places where traditional Internet connections are unavailable, unreliable, or significantly overburdened, such as on a battlefield, disaster zones, isolated rural areas, or crowded public venues. To enable collaboration among the devices in opportunistic networks, code offloading and Remote Method Invocation are the two major mechanisms to ensure code portions of applications are successfully transmitted to and executed on the remote platforms. Although these domains are highly enjoyed in research for a decade, the limitations of multi-device connectivity, system error handling or cross platform compatibility prohibit these technologies from being broadly applied in the mobile industry.
To address the above problems, we designed and developed UMSEF - an Universal Mobile Service Execution Framework, which is an innovative and radical approach for mobile computing in opportunistic networks. Our solution is built as a component-based mobile middleware architecture that is flexible and adaptive with multiple network topologies, tolerant for network errors and compatible for multiple platforms. We provided an effective algorithm to estimate the resource availability of a device for higher performance and energy consumption and a novel platform for mobile remote method invocation based on declarative annotations over multi-group device networks. The experiments in reality exposes our approach not only achieve the better performance and energy consumption, but can be extended to large-scaled ubiquitous or IoT systems.
|
| 4 |
[en] CAUSAL REASONING AND INDUCTION IN DAVID HUME / [pt] RACIOCÍNIO CAUSAL E INFERÊNCIA INDUTIVA NO PENSAMENTO DE DAVID HUMECARLOS JACINTO NASCIMENTO MOTTA 25 November 2005 (has links)
[pt] Esta dissertação tem por objetivo apresentar os resultados
da pesquisa de
mestrado em que se procurou evidenciar algumas
características da relação de
David Hume com a indução. Segundo a interpretação
corrente, Hume é o
responsável por mostrar que nossa razão não é capaz de
justificar qualquer um
de nossos raciocínios indutivos. O problema de Hume também
se caracteriza
por ser um problema acerca da racionalidade da ciência,
pois se seu método
principal, a indução, não pode receber suporte racional,
parece lícito afirmar
que o resultado de uma inferência indutiva é irracional. A
fim de delinear o
campo exato em que se insere a crítica humeana, este texto
irá mostrar como
Hume apresenta suas teorias acerca do raciocínio causal em
seu Tratado da
natureza humana, traçar as características exatas do
raciocínio causal de
Hume e confrontá-las com as formas de interpretação
presentes em alguns de
seus principais comentadores. Procuramos tornar claras as
falhas
apresentadas nestas interpretações. Em seguida trataremos
de discutir
algumas das mais celebradas interpretações da filosofia de
Hume, centrando
nossa análise nos textos de Mackie, Beauchamp e Mappes. O
capítulo final
tem por objetivo mostrar as características racionais que
podem ser atribuídas
aos raciocínios causais humeanos, salientando o caráter
particular de suas
inferências. Finalizando, mostraremos como a origem do
princípio da cópia
pode ser um exemplo do uso de inferências indutivas por
parte de Hume, o que
nos leva a considerações heterodoxas a respeito de sua
visão a respeito da
racionalidade. / [en] The aim of this work is to present the results of my
master´s degree research,
which tried to show some of the characteristics of David
Hume´s approach to
induction. According to the standard interpretation, Hume
is responsible for
showing that our reason is not able to justify any of our
inductive reasonings.
Hume´s problem also characterizes itself by being a
problem about the
rationality of science, for, since his main method,
induction, cannot receive a
rational foundation, it seems licit to assert that the
result of any inductive
inference is irrational. In order to precisely describe
the Humean criticism I am
going to show how Hume presents his theories concerning
causal reasoning in
this A Treatise of Human Nature, define the exact
characteristics of causal
reasoning according to him, and compare this analysis to
those by some of his
main critics. We shall try to bring to light the proposed
inadequacy of the latter.
Next we will discuss some of the most celebrated
interpretations of Hume´s
philosophy, specially those by of Mackie, Beauchamp and
Mappes. The final
chapter aims at showing the rational characteristics that
can be assigned to
Humean causal reasoning emphasizing the particular
character of his
inferences. Finally, we show how the origin of the copy
principle can be an
instance of the use of inductive inferences by Hume, which
allows us to risk
some heterodox hypotheses concerning his view of
rationality.
|
| 5 |
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.
|
| 6 |
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.5235 seconds