Current caching

Dominik Ruf dominikruf at gmail.com
Wed Jan 31 23:50:11 UTC 2018


Hi all,

I'm currently looking at the caching Kallithea does. And I'm a
bit...baffled.
The way I understand it is that first an entry is made to CacheInvalidation
to mark a cache invalid,
and later that entry is checked to decide if that cache should be
invalidated.
But why this detour? Why not invalidate the cache directly?
Can somebody explain to me why the invalidation is done via the
CacheInvalidation table?

cheers
Dominik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sfconservancy.org/pipermail/kallithea-general/attachments/20180131/ea1287a7/attachment.html>


More information about the kallithea-general mailing list