See http://trac.agavi.org/ticket/1095 / http://trac.agavi.org/changeset/4071 (both also mentioned in #1062).
On 05.01.2010, at 18:02, Guilherme Aiolfi wrote:
Is that $res variable visible in every template by default from 1.1 on?On Tue, Jan 5, 2010 at 11:53 AM, David Zülke <[email protected] > wrote:The main problem is that request attributes represent global state that is mutated by the action and the slots in question. Now if you cache a slot that also adds some javascript to this request attribute... you'll have to cache that request attribute as well, right? However, if that slot is used by another action as well, then when the cache for that slot is read, it restores the request attributes from the earlier run, where other slots had already set some javascript nto this request attribute, and boom, you get the wrong stuff in your output. Working around that with namespaces is extremely cumbersome; that's why as of 1.1, there are response attributes that are automatically cached and and merged properly (see http://trac.agavi.org/ticket/1062 for more details).
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
