Expiring cache key with 0.8.0

[chollier]

I know that 0.8.* is supposedly not supported anymore, however it seems to be the preferred stable branch right now as 0.10 will use the same API (if I understood right), or at least the same basics.

I'm trying to use the undocumented cache feature which seems to be super efficient for our use so far. However some of my serialized object have an high cache invalidation rate on the "running" state of their lifecycle. Also there are plenty of place where I should take care of that invalidation.

Hence, I'd rather set an expiration to something like 15min for those keys, is it something feasible without hacking the AMS code ?

[joaomdmoura]

Hi @chollier , one way to do this without hacking the AMS code would be to set an key to it using cache_key method and expiring it using a background job.

Btw, on 0.10.0 there will be a easier way to do this. You will be able to set it as an option when defining an serializer as cached. You can see examples of it on the PR #693

[steveklabnik]

@chollier , 0.8.x will still get bugfixes, it's just not undergoing new development. I'm giving this a close, because @joaomdmoura gave one answer, and because SO is a more appropriate question for 'how to use' than the Issues tracker, which we try to keep for bugs and feature discussion only.