A cache layer is always a critical and fragile structural element. It also breaks the direct and verifiable link between user and content, and add a delay between the update of the original file and its availability.
In this context cache is a band-aid, I would avoid it, focusing instead the energies on solving the issue at the source.
Login to reply
Replies (1)
yes, the root is that blossom still doesn't have a protocol for transcoded down-scaled versions