#809: Caching group element with array value support
----------------------------+-----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: david
Type: enhancement | Status: new
Priority: normal | Milestone: 0.11.3
Component: filter | Version: 0.11.2
Severity: normal | Resolution:
Keywords: | Has_patch: 0
----------------------------+-----------------------------------------------
Comment (by david):
Do you have more info regarding use case etc? Array access syntax is
currently only possible for parameter holders, not attribute holders... we
could change that, but it would slow everything down, so I'm reluctant to
do it.
also note that usually, you shouldn't have to use matched URLs as groups,
that's not how caches are supposed to work. they should be used in logical
contexts, not depending on how they are accessed. I assume that in your
case, the menu shows different kinds of information depending on what the
first matched route was. I'd change this so your baseview hands this
information as an argument to the slot (you can pull the slot container
after loadLayout(), no problem), and then the problem is not only gone,
but your code is also a lot more reliable.
--
Ticket URL: <http://trac.agavi.org/ticket/809#comment:2>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
