dido:public:ra:xapend:xapend.b_stds:tech:omg:dds
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:tech:omg:dds [2021/07/30 15:24] murphy |
dido:public:ra:xapend:xapend.b_stds:tech:omg:dds [2021/08/17 15:06] (current) murphy [Overview] |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| ==== Overview ==== | ==== Overview ==== | ||
| - | : //The DDS specification describes a [[dido:public:ra:xapend:xapend.a_glossary:d:dcps]] model for distributed application | + | : //The DDS specification describes a [[dido:public:ra:xapend:xapend.a_glossary:d:dcps]] model for [[dido:public:ra:xapend:xapend.a_glossary:d:dapp|distributed application]] |
| communication and integration. This specification defines both the Application Interfaces (APIs) and the | communication and integration. This specification defines both the Application Interfaces (APIs) and the | ||
| Communication Semantics (behavior | Communication Semantics (behavior | ||
| - | and quality of service) that enable the efficient delivery of information from information producers to matching | + | and [[dido:public:ra:xapend:xapend.a_glossary:q:qos|quality of service]]) that enable the efficient delivery of information from information producers to matching |
| consumers.// | consumers.// | ||
| * //The purpose of the DDS specification can be summarized as enabling the “Efficient and Robust Delivery of the Right Information to the Right Place at the Right Time.”// | * //The purpose of the DDS specification can be summarized as enabling the “Efficient and Robust Delivery of the Right Information to the Right Place at the Right Time.”// | ||
| - | : //The expected [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] domains require DCPS to be high-performance and predictable as well as efficient in its use of resources. To meet these requirements it is important that the interfaces are designed in such a way that they:// | + | : //The expected [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] domains require DCPS to be high-[[dido:public:ra:xapend:xapend.a_glossary:p:performance|performance]] and predictable as well as efficient in its use of resources. To meet these requirements it is important that the interfaces are designed in such a way that they:// |
| - | * //Allow the middleware to pre-allocate resources so that dynamic resource allocation can be reduced to the minimum,// | + | * //Allow the [[dido:public:ra:xapend:xapend.a_glossary:m:midware|middleware]] to pre-allocate resources so that dynamic resource allocation can be reduced to the minimum,// |
| * //Avoid properties that may require the use of unbounded or hard-to-predict resources, and// | * //Avoid properties that may require the use of unbounded or hard-to-predict resources, and// | ||
| * //Minimize the need to make copies of the data.// | * //Minimize the need to make copies of the data.// | ||
| Line 37: | Line 37: | ||
| by means of QoS settings offers the advantage that the application developer only indicates ‘what’ is wanted rather than ‘how’ this QoS should be achieved. Generally speaking, QoS is comprised of several QoS policies. Each QoS policy is then an independent description that associates a name with a value. Describing QoS by means of a list of independent QoS policies gives rise to more flexibility.// | by means of QoS settings offers the advantage that the application developer only indicates ‘what’ is wanted rather than ‘how’ this QoS should be achieved. Generally speaking, QoS is comprised of several QoS policies. Each QoS policy is then an independent description that associates a name with a value. Describing QoS by means of a list of independent QoS policies gives rise to more flexibility.// | ||
| - | : //This specification is designed to allow a clear separation between the publish and the subscribe sides, so that an application process that only participates as a publisher can embed just what strictly relates to publication. Similarly, an application process that participates only as a subscriber can embed only what strictly relates to subscription.// | + | : //This specification is designed to allow a clear separation between the publish and the subscribe sides, so that an application process that only participates as a [[dido:public:ra:xapend:xapend.a_glossary:p:publisher|publisher]] can embed just what strictly relates to publication. Similarly, an application process that participates only as a [[dido:public:ra:xapend:xapend.a_glossary:s:subscriber|subscriber]] can embed only what strictly relates to subscription.// |
dido/public/ra/xapend/xapend.b_stds/tech/omg/dds.1627673048.txt.gz · Last modified: 2021/07/30 15:24 by murphy
