Heartcore API caching (or, how can I see my changes immediately)
Hello,
I've noticed there's a lag time between when content changes and when that change is reflected in API calls.
For example, if I delete an item from the content tree, the Heartcore API will still return that item for a few minutes. So my application using the API is still showing it, even though it was just deleted by the user.
Here's another scenario:
Code calls API to check if an item with a certain name already exists. The API returns nothing. So we create the item with that name. In the backoffice, I end up with name (1) because the item actually did exist, but the API wasn't returning it yet.
Is there any way I can disable caching for the API? I'd prefer my applications use their own caching strategy and the API always returns the most up to date information.
Heartcore API caching (or, how can I see my changes immediately)
Hello,
I've noticed there's a lag time between when content changes and when that change is reflected in API calls.
For example, if I delete an item from the content tree, the Heartcore API will still return that item for a few minutes. So my application using the API is still showing it, even though it was just deleted by the user.
Here's another scenario:
Code calls API to check if an item with a certain name already exists. The API returns nothing. So we create the item with that name. In the backoffice, I end up with name (1) because the item actually did exist, but the API wasn't returning it yet.
Is there any way I can disable caching for the API? I'd prefer my applications use their own caching strategy and the API always returns the most up to date information.
Thanks, Joe
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.