Use native backend functionality to delete expired responses

[alessio-locatelli]

TO-DO

• MongoDB
  - How to implement: https://www.mongodb.com/docs/manual/tutorial/expire-data/
  - Implemented in requests-cache: yes.
• Redis
  - How to implement: Create a new hash with response_key: TTL and use a Lua server-side script to discard an expired response by the key. Use HEXPIRE.
  - Implemented in requests-cache: no.
• Sqlite: ?
• Filesystem?

Why

• Not necessary to run manually delete_expired_responses() if a backend supports TTL.
• Performance: no redundant network I/O if we only get a value to check that it has not expired.

Pull Request

(a draft) alessio-locatelli#1

[suraj-geddam]

Hi there. I was trying to follow your draft, but only implement the behavior for MongoDB. However, since expire_after wasn’t an optional parameter in the updated signature for write, I wasn’t sure how to proceed, as that would require updating every write call across all backends and tests.

If that’s the intended direction, no worries. I can drop my commits to avoid adding noise.