This will be at least used by WSNDeviceApp instances of Testbed Runtime to actively ask for currently attached devices. It is necessary to do so if the WSNDeviceApp instances is started after the DeviceObserver as it wouldn't get the events otherwise if it is not registering with the DeviceObserver directly as it is in the current implementation. In the current implementation an adapter TestbedApplication instance registers with the DeviceObserver and pushes events onto Testbed Runtimes newly introduced EventBus.
danbim
commented
12 years ago
This will be at least used by WSNDeviceApp instances of Testbed Runtime to actively ask for currently attached devices. It is necessary to do so if the WSNDeviceApp instances is started after the DeviceObserver as it wouldn't get the events otherwise if it is not registering with the DeviceObserver directly as it is in the current implementation. In the current implementation an adapter TestbedApplication instance registers with the DeviceObserver and pushes events onto Testbed Runtimes newly introduced EventBus.