ddsf:public:guidebook:06_append:02_quality_of_service:reader_data_lifecycle
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
ddsf:public:guidebook:06_append:02_quality_of_service:reader_data_lifecycle [2021/07/14 15:54] murphy ↷ Links adapted because of a move operation |
ddsf:public:guidebook:06_append:02_quality_of_service:reader_data_lifecycle [2021/07/14 15:55] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| The ''READER_DATA_LIFECYCLE'' policy controls the behavior of the DataReader with regards to the lifecycle of the data-[[ddsf:public:guidebook:06_append:glossary:i:instance|instances]] it manages, that is, the data-instances that have been received and for which the DataReader maintains some internal resources. | The ''READER_DATA_LIFECYCLE'' policy controls the behavior of the DataReader with regards to the lifecycle of the data-[[ddsf:public:guidebook:06_append:glossary:i:instance|instances]] it manages, that is, the data-instances that have been received and for which the DataReader maintains some internal resources. | ||
| - | The ''DataReader'' internally maintains the [[ddsf:private:guidebook:06_append:glossary:s:sample|samples]] that have not been taken by the application, subject to the constraints imposed by other [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] policies such as ''[[ddsf:public:guidebook:06_append:glossary:h:history_qos|HISTORY]]'' and ''RESOURCE_LIMIT''. | + | The ''DataReader'' internally maintains the [[ddsf:public:guidebook:06_append:glossary:s:sample|samples]] that have not been taken by the application, subject to the constraints imposed by other [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] policies such as ''[[ddsf:public:guidebook:06_append:glossary:h:history_qos|HISTORY]]'' and ''RESOURCE_LIMIT''. |
| The ''DataReader'' also maintains information regarding the identity, ''view_state'' and ''instance_state'' of data-instances even after all samples have been ‘taken.’ This is needed to properly compute the states when future samples arrive. | The ''DataReader'' also maintains information regarding the identity, ''view_state'' and ''instance_state'' of data-instances even after all samples have been ‘taken.’ This is needed to properly compute the states when future samples arrive. | ||
ddsf/public/guidebook/06_append/02_quality_of_service/reader_data_lifecycle.1626292441.txt.gz · Last modified: 2021/07/14 15:54 by murphy
