that each such identifier or class name is prefixed with an authority indicator. For example,
CORBA uses text strings to name object classes. In TOAD, an object class name based on
CORBA consists of the CORBA authority prefix, followed by the CORBA text string name of
the class.
networks usually have proprietary interfaces. This precludes inexpensive aftermarket
addition or replacement of components in the automobile, since each component must
be designed for a few specific models of automobile.
networked, and defined using standard object interfaces.
The alarm could discover the console (to provide a user interface, possibly as a window
on a generic display), lights and horn (to flash or sound in case of violation), engine (to
shut down when there is no authorization), and sound system (to provide voice
interfaces or warning messages). Little or no rewiring would be required.
radio, for example, to reduce its volume during calls. The existing sound system might
be used for audio communication with the vehicle’s occupant.
network topologies in the automobile. For instance, one vehicle design might have
separate sound systems for front and rear compartments. A TOAD-compliant manager
node could arbitrate requests for resources among such multiple sound systems, and
the original component need not have anticipated its use in such an environment.
the internet, for remote diagnostics, maintenance, or software upgrades. This function
is enhanced by use of the TOAD protocol, since it allows operations such as outright
replacement (on the network) of an automobile’s components by alternative, remote
software components.
contain a broker or directory service at a well-known address to facilitate these
functions. If well-known addresses were used for all components, the broker might not
be necessary, but on-the-fly replacement of components for diagnostic or maintenance
purposes would not be practical.