Dynamic TTL

[caeus]

Dynamic TTL

[glockbender]

It is such a good and useful enhancement and it would be awesome to have it in this lib.

[Shabinder]

we even have kotlinx.datetime which should make this simpler to impl for all platforms in commonMain only.

[ychescale9]

Thanks everyone, I might take a look at this soon.

Can you share a few examples of your use cases and how you think the APIs should look like? Is this a feature you've used in other caching libraries in the past?

[glockbender]

Example of function description:

public data class LoaderContext internal constructor(
    var expireAfterAccessDuration: Duration,
    var expireAfterWriteDuration: Duration
)

public suspend fun get(key: Key, loader: suspend LoaderContext.() -> Value): Value
// looks like it should be a new 'put' function with 'customizing'
public suspend fun put(key: Key, loader: suspend LoaderContext.() -> Value)

Example of usage:

suspend fun cacheToken(key: String, ttl: Duration): Any {
   cache.put(key) {
      // by default cache-level configured values are set
      this.expireAfterAccessDuration = ttl
      // ...
   }
}

suspend fun someFun(key: String, ttl: Duration): Any {
   cache.get(key) {
      this.expireAfterWriteDuration = ttl
      // ...
   }
}

Is this a feature you've used in other caching libraries in the past?

Using it a lot with Redis

[caeus]

I'd add the feature as part of the builder:

dynamicExpireAfterWrite{ it.expires_in.seconds }