retrostash-okhttp/dev.logickoder.retrostash.okhttp/RetrostashOkHttpConfig

RetrostashOkHttpConfig

data class RetrostashOkHttpConfig(val timeoutMs: Long = 250, val maxEntries: Int = 64, val maxBytes: Long = 2 * 1024 * 1024L, val defaultMaxAgeMs: Long = 10 * 60 * 1000L, val logger: (String) -> Unit? = null, val cacheDirName: String = "retrostash_okhttp_cache", val prefsName: String = "retrostash_okhttp_store")

Tunables for RetrostashOkHttpInterceptor and AndroidRetrostashStore.

Caching strategy

Retrostash maintains its own annotation-driven cache (the dev.logickoder.retrostash.core.RetrostashStore). Treat it as the only Retrostash-controlled cache layer. If you also pass cache(...) to your OkHttpClient.Builder, OkHttp's HTTP disk cache obeys origin Cache-Control headers independently — Retrostash invalidation does not evict OkHttp HTTP cache entries.

Most apps want exactly one cache layer. Drop cache(...) from your OkHttpClient.Builder and let Retrostash own the lifecycle. See Caching strategy.

Constructors

RetrostashOkHttpConfig

constructor(timeoutMs: Long = 250, maxEntries: Int = 64, maxBytes: Long = 2 * 1024 * 1024L, defaultMaxAgeMs: Long = 10 * 60 * 1000L, logger: (String) -> Unit? = null, cacheDirName: String = "retrostash_okhttp_cache", prefsName: String = "retrostash_okhttp_store")