This has been around for a number of years, and it implements the design pattern of aMaster Page.

In fact this predates the deployment of Master Pages in ASP/Visual Studio .Net.
Yes, you saw it in Cold Fusion first !!
Fusebox was around before Microsoft released he first version of VS.Net around 2003/4?)

Cheers,
BP

I agree. Meanwhile combination of and does the job.

Thanks for the comment, my intention of this post was towards the audience that’s not using any sort of MVC framework (sorry did not make it very clear), I completely agree that many coldfusion MVC framework out there support the template based system i.e. like in fusebox can have global header and footer and respective views for the individual pages. But what I find missing (strictly focusing on fusebox in this context) is that once certain section of template is executed or rendered there are no possible changes, whereas in asp.net masterpage that’s not the case, the template and content gets merged after the server side logic has completely processed, and that’s what I wanted to highlight in this post.

Also thanks for highlight the cfsavecontent limitation, you are correct to point out that cfform and cf8 ajax template adds extra content that cannot be capture in cfsavecontent tag.

My intention of this post was to throw out some thought provoking idea on notion of generating the content first and then merging it with template completely against the normal way of procedural rendering of content.

BTW: you got great documentation on coldfusion MVC frameworks!

reference: http://on.tapogee.com/galleonproject/comparison.html#views

warning: CFSAVECONTENT does not everything. CFFORM and cf8 ajax tags are examples of tags that don’t get ’saved’.