docs(ssr): clarify that generation counters are future-ready infrastructure
This commit is contained in:
parent
7f372446da
commit
668920e9fb
@ -24,9 +24,9 @@ MAX_SESSIONS_PER_USER=5
|
|||||||
DB_POOL_SIZE=20
|
DB_POOL_SIZE=20
|
||||||
|
|
||||||
# SSR page cache duration in seconds (default: 3600).
|
# SSR page cache duration in seconds (default: 3600).
|
||||||
# Generation-based invalidation is implemented in src/ssr_cache.rs and bumps on every post
|
# src/ssr_cache.rs maintains a global generation counter bumped on every post write, but
|
||||||
# write. However, Dioxus 0.7 does not expose a public API to customize the incremental SSR
|
# Dioxus 0.7 does not expose an API to wire it into the incremental SSR cache key. Until such
|
||||||
# cache key, so SSR_CACHE_SECS remains the effective fallback TTL until such API is available.
|
# an API is available, this TTL is the only effective SSR cache invalidation mechanism.
|
||||||
SSR_CACHE_SECS=3600
|
SSR_CACHE_SECS=3600
|
||||||
|
|
||||||
# Image serving cache headers (hardcoded defaults)
|
# Image serving cache headers (hardcoded defaults)
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user