This device/service illustrates my idea of how the interface
between the "hardware/simulated" and "PalcomThread" domains
is implemented.

All communication between the two domains is done using the
methods of the IDeviceIO interface. The interface specifies 
operations to allow both event-based and polling I/O, in 
both directions.

Having such an interface isolates the PalcomThread parts of
the code from the hardware/GUI/java.lang.Thread-specific 
details of the "hardware/simulated". Thus the code on the
"PalcomThread" side should be generic and work on both
the simulated device and under PalVM on the actual hardware.


In the example, with only event-based communication, it looks
like this:
-----------------------------------------------------------------

                                putEvent +--------+
                              +--------->|IOThread|---+
                              |          +--------+   |
                              |          +--------+   | (method call*:
                              |          +--------+   |  doTickCommand)
                              |                       V
+-----------+ putEvent   +--------- + putEvent +------------+
| Timer H/W |----------->| DeviceIO |<---------|TimerService|
+-----------+            +----------+          +------------+
+-----------+ callback   +----------+          +------------+
|           |<-----------|          |          |            |
+-----------+            +----------+          +------------+


* This call is part of the internal implementation of the service,
  and not part of the I/O implementation. It is shown here for 
  completeness.

-----------------------------------------------------------------

Initalization of "main" classes and of I/O related stuff:

In the main method:
	Create a new TimerDevice
		in CreateDeviceContext:
			TimerDevice creates a new TimerIO
			TimerDevice creates a new TimerDeviceContext, pass timerIO
	Create a new SimulatedTimer, pass context.getIO()

In TimerService.start():
	create a new TimerIOThread, schedules it and register it as an
	inEventReceiver in the IO object