Ad-Hoc Services:
Contents
1 Introduction 2
2 Performance Measures 3
2.1 Testing what? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Testing communication with a small amount of data . . . . . . . . . . . 3
2.3 Testing communication with a big amount of data . . . . . . . . . . . . 3
2.4 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 A Framework for System Wide Accessible Services 6
3.1 Demands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Changing the Communication Technology . . . . . . . . . . . . . . . . . 8
3.4 Open Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 Service Compiler for RMI Framework 9
4.1 Purpose of Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2 Description of Finite State Machines . . . . . . . . . . . . . . . . . . . . 9
4.3 Usage of Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.4 Requirements of Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 Implementing new Services 12
5.1 Requirements of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2 Implementing a new Service . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.3 Using Services in Applications . . . . . . . . . . . . . . . . . . . . . . . . 12
6 Ad-Hoc-Services 13
6.1 General design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.2 Basic Ad-Hoc-Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2.1 Neighborhood service . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2.2 Forwarding service . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2.3 Sni er service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3 Non-Basic Ad-Hoc-Services . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.1 Flooding service . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.2 Messaging service . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.3 Noti er service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7 Conclusions 17
Chapter 1
Introduction
The objective of this thesis was to implement some basic ad-hoc services which can be used by Java applications running on the system. To realize this task, we needed a framework which allows applications to access the functions of the services. The services should be started at the start-up of the machine and run in the background.
One of the demands was that the applications should not need to know anything about the kind of communication that is used between the application and the service.
It should be possible to add new services to the existing framework, too. Another requirement was that it is possible to easily exchange the communication technology without changing services and applications. Chapter 3 describes the architecture of the framework we designed for those demands. Chapter 4 describes the compiler which is used to add new services to the machine.
Another aspect we paid attention to was performance. For selecting the right communication, we measured di erent kinds of communication for the messaging between the two Java Virtual Machines (Application - Services). In chapter 2 the results of these measurements are described.
Contents
1 Introduction 2
2 Performance Measures 3
2.1 Testing what? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Testing communication with a small amount of data . . . . . . . . . . . 3
2.3 Testing communication with a big amount of data . . . . . . . . . . . . 3
2.4 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 A Framework for System Wide Accessible Services 6
3.1 Demands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Changing the Communication Technology . . . . . . . . . . . . . . . . . 8
3.4 Open Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 Service Compiler for RMI Framework 9
4.1 Purpose of Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2 Description of Finite State Machines . . . . . . . . . . . . . . . . . . . . 9
4.3 Usage of Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.4 Requirements of Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 Implementing new Services 12
5.1 Requirements of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2 Implementing a new Service . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.3 Using Services in Applications . . . . . . . . . . . . . . . . . . . . . . . . 12
6 Ad-Hoc-Services 13
6.1 General design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.2 Basic Ad-Hoc-Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2.1 Neighborhood service . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2.2 Forwarding service . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2.3 Sni er service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3 Non-Basic Ad-Hoc-Services . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.1 Flooding service . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.2 Messaging service . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.3 Noti er service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7 Conclusions 17
Chapter 1
Introduction
The objective of this thesis was to implement some basic ad-hoc services which can be used by Java applications running on the system. To realize this task, we needed a framework which allows applications to access the functions of the services. The services should be started at the start-up of the machine and run in the background.
One of the demands was that the applications should not need to know anything about the kind of communication that is used between the application and the service.
It should be possible to add new services to the existing framework, too. Another requirement was that it is possible to easily exchange the communication technology without changing services and applications. Chapter 3 describes the architecture of the framework we designed for those demands. Chapter 4 describes the compiler which is used to add new services to the machine.
Another aspect we paid attention to was performance. For selecting the right communication, we measured di erent kinds of communication for the messaging between the two Java Virtual Machines (Application - Services). In chapter 2 the results of these measurements are described.
DOWNLOAD LINK:
No comments:
Post a Comment