Caching behaviour and invalidation in Lychee

[kiancross]

I've been experimenting with the caching feature that was introduced in Lychee and I'm trying to better understand when the cache is expected to be invalidated.

In a few cases, the UI doesn't seem to update until I manually click 'Flush cache', for example:

• Creating an album - the new album doesn't appear inside its parent album.
• Uploading a photo - the photo doesn't appear in the target album.

On the other hand, deleting an album does seem to update the UI immediately.

Is this behaviour expected?

For reference, I'm currently running v6.10.4. I haven’t had time to upgrade to v7 yet, so it's also possible this has already been addressed there.

Any clarification would be appreciated.

[ildyria]

Hi,

There are two caches in Lychee taking action.

The browser side cache which uses https://www.npmjs.com/package/axios-cache-interceptor You can see it in action here: https://github.com/LycheeOrg/Lychee/blob/master/resources/js/services/album-service.ts#L84 It is usually cleared manually when doing actiongs on the frontend (or simply pressing F5).

And the serverside cache:

• https://github.com/LycheeOrg/Lychee/blob/master/app/Http/Middleware/Caching/ResponseCache.php
• https://github.com/LycheeOrg/Lychee/blob/master/app/Http/Middleware/Caching/AlbumRouteCacheRefresher.php <- this one is supposed to hook on requests and dispatch a Cache clear event for targeted set of albums:
• https://github.com/LycheeOrg/Lychee/blob/master/app/Listeners/AlbumCacheCleaner.php

To be honest, the implementation is not as ironclad as I wished it to be and probably need to be refactored.
That said with version 7, the caching utility has been significantly reduced.

[kiancross]

Ok, thanks. I'll try upgrading to v7 today or tomorrow.