Hi, Reading through our caching code, I wondered why we don't make it a bit more clever. For every dynamically created page, we could just store a fingerprint that can be computed quite fast and indicates whether the cache slot is still up-to-date or not.
For example, on the log pages, we could save the commit the corresponding ref points to and invalidate the cache slot when the ref has changed. Using that, we could use the power of caching and never deliver outdated pages at the same time. What do you think about that? Regards, Lukas _______________________________________________ CGit mailing list CGit@lists.zx2c4.com http://lists.zx2c4.com/mailman/listinfo/cgit