`ttl` option of `utils.cache`

[ehmicky]

utils.cache has a ttl option. Would this work for this plugin?

[itzsaga]

The upside to the current implementation is the ttl can be backwards applied to formerly cached assets if needed.

[ehmicky]

The main difference with utils.cache's ttl option is in the timestamp stored in cache:

• It uses a single timestamp per cached directory, while this plugin uses each file's mtime
• The timestamp is created each time utils.cache.save() is called, as opposed to when the file was last modified

Based on this, it does look like this might not work for you use case. What do you think?

[itzsaga]

No particular use case. Just wanted to highlight the differences for discussion 😃.

[ehmicky]

If you think the ttl option would not work for this plugin, please feel free to close this issue. I am not quite sure whether that option would be helpful or not for you. :)