ROAF and GTS Analogies
Although the Book is completely avoiding the terms Tracking System and Tracking Devices
the reader can easily identify the major components:
- a RealObjectApplication as a GPS Tracking System (or Server)
- a RealObject as a Tracking Device (or Client) and
- Remote Method Invocation (RMI) as the (preliminary?) Transfer Protokol (ROAP?).
The Book has not envisioned 'Real World Simulations' from existing technologies. The idea was simply to monitor every Thing and to synchronize all Things in a Scenario. Tracking Systems provide technological components to hook up Tracking Devices and store their information in a Database:
- a Database (abstracted via JDBC) to persist ServerObject history and relate any other information
- OpenLayer as a general purpose Map GUI to hook up various free or commercial map servers
or your private OpenStreetMap created with the map compiler introduced in the book
- the Webcontainer Tomcat to deploy Java Server Pages (JSPs) and Java Servlets as webfrontend GUIs to access the ROAF and manage users and sessions.
Without going into the details of what can be done with these Technologies the OpenGTS represents the Gateway from the roaf Packages to the World Wide Web. And much more than that the actual GTS serves as an abstraction layer of the actual tracking hardware! The roaf.de/velopment should not be slowed down by dealing with hardware drivers. Technically the roaf layer has to provide ways to bundle Real World Data and provide it to other ROApps.
|« GTS components||todo »|