As discussed the other day with @benoit74, it makes little sense in the library.kiwix.org infra to always request and receive the whole catalog from the CMS, then parse it and compare with a local copy to find out what changed and clear the cache for those books.
@kelson42 suggested we could send a datetime as input and the CMS would only return books published (added, modified) since that date.
While it would indeed work for new or updated ZIMs, it would not inform about any removal (unpublish) from the Catalog which defeats the core purpose of the CMS.
Supporting deletions would imply using a custom format instead of the plain old Library XML.
I am opening this issue to record the discussion but I think that we should proceed as planned for the moment.
We can later improve with a more sophisticated solution. I think the pub/sub pattern would be a good candidate.
As discussed the other day with @benoit74, it makes little sense in the library.kiwix.org infra to always request and receive the whole catalog from the CMS, then parse it and compare with a local copy to find out what changed and clear the cache for those books.
@kelson42 suggested we could send a datetime as input and the CMS would only return books published (added, modified) since that date.
While it would indeed work for new or updated ZIMs, it would not inform about any removal (unpublish) from the Catalog which defeats the core purpose of the CMS.
Supporting deletions would imply using a custom format instead of the plain old Library XML.
I am opening this issue to record the discussion but I think that we should proceed as planned for the moment.
We can later improve with a more sophisticated solution. I think the pub/sub pattern would be a good candidate.