#701: View cache validity check does not use lifetime, might cause usage of
stale
data
--------------------+-------------------------------------------------------
Reporter: david | Owner: david
Type: defect | Status: new
Priority: high | Milestone: 0.11.1
Component: filter | Version: 0.11.0
Severity: major | Keywords:
Has_patch: 0 |
--------------------+-------------------------------------------------------
Consider this situation:
* Action with two output types
* Caching configured with a lifetime
* Expired caches for both output types exist
Now if this happens:
* Action is called with OT1, cache is expired, so action is run again,
and cache is written again
* View is run for OT1, too, since Action cache was expired, and cache is
written again
Then we are in trouble:
* A following call with OT2 within the lifetime pulls the action results
from the cache
* Because the view cache check does not check for a lifetime, the stale
cache for OT2 is used
--
Ticket URL: <http://trac.agavi.org/ticket/701>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
