dido:public:ra:xapend:xapend.a_glossary:i:instance
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.a_glossary:i:instance [2021/07/26 12:36] murphy |
dido:public:ra:xapend:xapend.a_glossary:i:instance [2021/10/04 12:37] (current) 185.191.171.33 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Instance ===== | ===== Instance ===== | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary | Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| Line 16: | Line 16: | ||
| * [[dido:public:ra:xapend:xapend.a_glossary:s:scalable|Scalability]] when representing many thousands of objects - you can use a single DataReader to receive the state of all the instances within a topic | * [[dido:public:ra:xapend:xapend.a_glossary:s:scalable|Scalability]] when representing many thousands of objects - you can use a single DataReader to receive the state of all the instances within a topic | ||
| - | * Quality of Service applied per-instance: Some quality of service behaviors are applied per-instance. For example, the [[dido:public:ra:xapend:xapend.a_glossary:h:history_qos|HISTORY QoS]] is applied per-instance, which allows you to store a certain number of updates for every instance. Note that you cannot specify different QoS for specific instances within the same DataWriter or DataReader. The QoS is set on the writer or reader, and applied on each instance. A description of all QoS, including information on which QoS policies are applied per-instance is here. | + | * Quality of Service applied per-instance: Some [[dido:public:ra:xapend:xapend.a_glossary:q:qos|quality of service]] behaviors are applied per-instance. For example, the [[dido:public:ra:xapend:xapend.a_glossary:h:history_qos|HISTORY QoS]] is applied per-instance, which allows you to store a certain number of updates for every instance. Note that you cannot specify different QoS for specific instances within the same DataWriter or DataReader. The QoS is set on the writer or reader, and applied on each instance. A description of all QoS, including information on which QoS policies are applied per-instance is here. |
| * Life-cycle information is available for instances: A receiving [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] can detect whether an instance is alive or not. A sending application can change the instance state. | * Life-cycle information is available for instances: A receiving [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] can detect whether an instance is alive or not. A sending application can change the instance state. | ||
| * Efficient filtering of data by key fields: If you are only interested in receiving updates about certain instances, you can set up a content-filter for certain values of the key fields. This filtering is particularly efficient if you are only filtering on key fields. | * Efficient filtering of data by key fields: If you are only interested in receiving updates about certain instances, you can set up a content-filter for certain values of the key fields. This filtering is particularly efficient if you are only filtering on key fields. | ||
dido/public/ra/xapend/xapend.a_glossary/i/instance.1627317412.txt.gz · Last modified: 2021/07/26 12:36 by murphy
