Glossary

The glossary includes definitions for terms which are commonly used here, and that are part of the DDS and RTI lexicon.

A key field is member field of your data type that represents part of a unique identifier of your data - much like a primary key in a database. All key fields combined are called a key, and should form a unique identifier of an element (called an instance ) within your Topic. One example of a key
8785 reads — 0 comments
A locator is a combination of a transport kind, address and port number. Sometimes in string format, sometimes specified in a DDS_Locator_t structure. Examples: ( DDS_LOCATOR_KIND_UDPv4 , 10.10.1.121, 7400) or "udpv4://10.10.100.21:7400"
1593 reads — 0 comments
Middleware is a software layer between an application and the operating system. Network middleware isolates the application from the details of the underlying computer architecture, operating system and network stack (see Figure 1 ). Network middleware simplifies the development of distributed
5573 reads — 0 comments
Point-to-point is the simplest model of communication , as illustrated in Figure 1; it is a model of one-to-one communications. The telephone is an example of an everyday point-to-point communications device. To use a telephone, you must know the address (phone number) of the other party. Once a
3329 reads — 1 comment
Publish-Subscribe . In the publish-subscribe communications model (Figure 1), computer applications (nodes) “subscribe” to data they need and “publish” data they want to share. Messages pass directly between the publisher and the subscribers, rather than moving into and out of a centralized server
3885 reads — 0 comments
QoS (Quality of Service) in DDS (Data Distribution Service) are a set of configurable parameters that control the behavior of a DDS system, such as resource consumption, fault tolerance, and communication reliability. Each entity (Topic, DataReader, DataWriter, Publisher, Subscriber, and
6797 reads — 2 comments
Introduction We come up with system requirements so that we can specify what we want our system to be. Among other things, this allows us to communicate what we want the system to do and how it should operate so that when someone goes to the design and architecture phase, they have a place to start
1690 reads — 0 comments

Pages