aweakley
aweakley
That didn't fix it for me I'm afraid. I've pulled d9ef74c and I'm getting the same behaviour.
@cogat That sounds like a great Idea. Please can you fork the repo and make a pull request when you're ready?
This is what we're seeing: - visit the homepage, - homepage response is cached, - keyring updated to include homepage cache key - (some time later) visit another page -...
I was wondering if we should clean up the keyring each time we come to add something to it, but that felt like it might be too expensive during the...
Alternatively, rather than having one single keyring with everything in it, how about having a separate item for each cached url? Then they'd each have their own expiry time, which...
I think it might be better to use the database to store the combination of URL, cache key and timeout. That would make it easy to get the cache keys...
I was worried about the speed of automatically purging during the request/response cycle if there are lots of things to purge. But I guess if it’s done each time an...
I've had a go at that in https://github.com/ixc/wagtail-cache/tree/keyring_in_database and we're testing now to see how it goes.
I've just reverted this to draft because we're finding that calling `clear_expired()` during `set()` is not thread safe.
It's not ASGI, but there are lots of servers and workers. We were getting many concurrent requests creating calls to `set` and they were each creating a `clear_expired` query on...