When I started to make a concept about the implementation of my client server architecture I only knew
that I had to use Java. So I had to discover its packages to get an idea how to do it with that
language. To use java.rmi.* seemed to be the easiest way to do it.
Also the java.net package provides a programmer with the possibility to implement a client and a server. But its classes seemed much too complicate for an absolute novice that I am in the field of network.programming
In fact there has been much too less time to do all the tasks that had to be done for the application. So I was happy to have at leats for the connection module a very easy way to implement it.
Implementing a remote object with java.rmi packages means to implement a remote interface that has
been extended from the
It is the definition of the protocoll used for connections to objects that implement this interface.
The interface of the first version of my client is shown in the table below. With it my client was able to receive some messages from a connected remote object.
The interface of the first version of my server is shown in the next table. With it the server was able to register a remote object to unregister a registered object and to receive some messages from a connected remote object.
These interfaces were implemented by the
In a later version of the client and server interfaces these interfaces became one, having only one method.
The Task to be executed is another interface, the implementations of which can be executed by the
runTask function of every implementation of the
That doesn't actually mean that we have less source code. It only makes it much easier to extend the functionality of client or server. For that I have to add some Tasks only.
[startpage] [project part 1] [project part 2] [week 1] [week 2] [week 3] [week 4] [week 5] [week 6] [week 7] [week 8] [week 9] [week 10] [week 11] [References]