Understand how to implement a "technical cache" to extend native Odata applications that use an online OData store for read requests in environments where the application is occasionally offline due to network issues. CUD requests do not go through the cache.
The OData API includes functions that returns previously queried results to the online application, which is useful in scenarios where an online application executes read queries then goes offline due to network connectivity issues. The developer can include application logic that identifies if the data is fresh or not, and can make a request for a forced refresh, which may fail if there is no connection to the server. This section describes the requirements to extend an online OData application to an occasionally offline OData application.