#742: Change execution filter to run action again if action is cached, but
output
type of the view isn't
--------------------+-------------------------------------------------------
Reporter: david | Owner: david
Type: task | Status: new
Priority: normal | Milestone: 0.11.1
Component: filter | Version: 0.11.0
Severity: major | Resolution:
Keywords: | Has_patch: 0
--------------------+-------------------------------------------------------
Comment (by david):
The plan:
* if no {{{<action_attributes>}}} are defined, the Action will be run
again if a cached version of the Action exists, but no cached (or a stale)
version of the View
* the result of the newly run Action is written to the cache
* also, if the View name returned by this Action run differs from what's
in the cache, all existing View caches will be purged, provided that the
new View name is on the list of cacheable Views
* if the returned View name is not on the list of cacheable Views, all
existing View caches will be purged and the (now definitely stale) Action
cache will be removed
* a configuration flag could be used to allow people the disabling of
View cache flushing for the situation where the View names differ, but the
new View name is also allowed to be cached
--
Ticket URL: <http://trac.agavi.org/ticket/742#comment:3>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
