Caching on views and nested event-handlers.

[andrea@…]

I have created a patch that enable MG to cache single view based on include tag and also events differents from the main one. Actually these 2 caching scenario are not working at all.

<event-handler name="page.index" >

<broadcasts /> <results> <result do="views.one"/> <result do="views.two"/> <result do="template.main" /> </results> <views> <include name="three" template="pages/three.cfm" cache="true" /> <include name="four" template="pages/four.cfm"/> </views> </event-handler>

<event-handler name="views.one" cache="true"> <views> <include name="one" template="pages/one.cfm" /> </views> </event-handler>

<event-handler name="views.two"> <views> <include name="two" template="pages/two.cfm" /> </views> </event-handler>

Code like this will work efficiently.

[boomfish]

Caching views and queued events is a complex issue and the provided patch does not address all the current concerns.

Dan Wilson has asked me to propose a specification for the caching of views and queued events with an implementation targeted for the 3.2 release.

[boomfish]

Closing this ticket as a duplicate of #377.