Extending the life of object in cache¶
There are two way to extend object's life in cache - relative timeframe and fixed timeframe. With the relative timeframe a period of time is added to the timestamp of the call to determine the new expiration time. The fixed timestamp approach sets the timestamp when the object must expire from cache.
xxxx.backendless.app is a subdomain assigned to your application. For more information see the Client-side Setup section of this documentation.
||identifies the object to extend the life of in cache.|
||number of seconds to extend the life of object in cache by. Must be a value between 1 and 7200 (2 hours).|
||a timestamp in milliseconds when the object should expire and removed from cache. The difference between
Content-Type: application/json user-token: optional value obtained as a result of the login operation.
||Must be set to
||Optional header. Contains a value returned by Backendless in a preceding user Login API call. If
Make sure to replace xxxx in the domain name in the sample request below to the one assigned to your application.
Relative time extension:
curl -X PUT \ https://xxxx.backendless.app/api/cache/myorder/expireIn?timeout=1200
Absolute time extension:
curl -X PUT \ https://xxxx.backendless.app/api/cache/myorder/expireAt?timestamp=1407213507898