Expiring entries #8

New issue

Open

opened 2023-05-27 18:34:30 +02:00 by Jef Roosens · 0 comments

Jef Roosens commented

2023-05-27 18:34:30 +02:00

Owner

Automatically removing an entry after a period of time could be useful, e.g. if we know the entry won't be useful or relevant anymore after a certain date.

The expiry time can be sent as an X-Lander header as a Unix epoch, and the CLI tool can parse more human-friendly formats where needed.

In terms of implementing the actual removal, I currently see two main ways to deal with this:

Remove an entry the moment it's being requested after it has expired. This has the advantage of not having to implement any sort of background work, but it could let entries stay on disk for much longer than intended.
Implement a background worker thread that takes care of this work. This would fix the above issue, but it would introduce a new level of complexity.

Automatically removing an entry after a period of time could be useful, e.g. if we know the entry won't be useful or relevant anymore after a certain date. The expiry time can be sent as an `X-Lander` header as a Unix epoch, and the CLI tool can parse more human-friendly formats where needed. In terms of implementing the actual removal, I currently see two main ways to deal with this: * Remove an entry the moment it's being requested after it has expired. This has the advantage of not having to implement any sort of background work, but it could let entries stay on disk for much longer than intended. * Implement a background worker thread that takes care of this work. This would fix the above issue, but it would introduce a new level of complexity.