-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CMS Updated API #482
Comments
Is there an API call, SQLite query, or file folder check that I can do to determine if the CMS has been updated? That way, I can do a quick check with that (building my own wrapper if necessary) on the loading of a website, rather than pulling from the CMS API each time for all content. |
Okay, I get it. It's yaml. I thought this content was being stored in SQLite. However, it's not. Okay, so basically,
|
@volomike I think there should be some kind of Client SDK (php,js,python and etc...) that will fetch data from API and will store it in the locale cache for some time |
Most people using a headless CMS will want to connect with the FlexType API and then handle caching on the website, rather than the admin system. Imagine if you will the admin system is on a subdomain, while the main website is on the main domain. In building that cache code for the website, one needs to know when that cache is invalid and needs to be retrieved again. It would be great if, every time some Entry is added, changed, or removed, no matter the entry, it stores a "cms-last-modified" timestamp value somewhere, and then make that available on the API. This API should respond as fast as possible and then disconnect. So, when someone loads a website, it does this API call to the admin system to ask, "Is my cache invalid and I need to re-download everything again?" If the cache is still valid on the website side, then it could pull from cache instead of pulling from the CMS system. And, you could build a failsafe where the website will mark the cache invalid on either an interval like once a day or once a week.
What I'm having to do now, without this solution, is to just make live calls to the CMS every time the website loads, which can make a site slow.
The text was updated successfully, but these errors were encountered: