Closed CDR-Register-Stream closed 3 years ago
The public APIs GetDataRecipient , GetDataRecipientsStatus and GetSoftwareProductsStatus are deployed to a CDN and are expected to be polled at the rates defined in Cache Update Periods.
The CDN supports ETags and the expectation is that clients would use these tags for change detection to minimise the amount of data they are pulling and processing.
The documentation needs to outline this functionality and define best practice
ETag support now documented in the Participant Statuses section of the CDR Register design
Closing as issue now addressed in V1.3.0 of the CDR Register design
The public APIs GetDataRecipient , GetDataRecipientsStatus and GetSoftwareProductsStatus are deployed to a CDN and are expected to be polled at the rates defined in Cache Update Periods.
The CDN supports ETags and the expectation is that clients would use these tags for change detection to minimise the amount of data they are pulling and processing.
The documentation needs to outline this functionality and define best practice