Commit 78ab678f authored by Geoff Simmons's avatar Geoff Simmons

Another rewording for req.ttl in the 6.1 release notes.

parent 0c823a89
...@@ -50,12 +50,12 @@ since there are use cases that cannot be solved without it. Similarly, ...@@ -50,12 +50,12 @@ since there are use cases that cannot be solved without it. Similarly,
``req.ttl`` used to be deprecated and is now fully supported again. ``req.ttl`` used to be deprecated and is now fully supported again.
``req.ttl`` and ``req.grace`` limit the ttl and grace times that are ``req.ttl`` and ``req.grace`` limit the ttl and grace times that are
permitted for the current request. If ``req.ttl`` is set, it requires permitted for the current request. If ``req.ttl`` is set, then cache
cache objects to have that minimum remaining ttl to be considered objects are considered fresh (and may be cache hits) only if their
fresh. Likewise, ``req.grace`` sets an upper bound on the time an remaining ttl is less than or equal to ``req.ttl``. Likewise,
object has spent in grace to be considered eligible for grace mode ``req.grace`` sets an upper bound on the time an object has spent in
(which is to deliver this object and fetch a fresh copy in the grace to be considered eligible for grace mode (which is to deliver
background). this object and fetch a fresh copy in the background).
A common application is to set shorter TTLs when the backend is known A common application is to set shorter TTLs when the backend is known
to be healthy, so that responses are fresher when all is well. But if to be healthy, so that responses are fresher when all is well. But if
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment