> Allaire's docs state that it'll be faster that a "custom tag
> solution"... meaning cf_bodycontent, I assume.
Meaning faster than using ThisTag.GeneratedContent with custom tags.
> I don't plan to use it myself, mainly because I make a lotta use
> of a modified cf_bodycontent that creates arrays of content...
I think you could as well use this new tag to do this. Example:
<cfset request.content = StructNew()>
<cfsavecontent variable="request.content.leftMenu">
some code here that generates navigation menu
</cfsavecontent>
And in some other place for an example
<cfsavecontent variable="request.content.body">
some code here that generates the page body (news item etc.)
</cfsavecontent>
And at the end of index.cfm in app_layout.cfm you put it together again
using the request.content.leftMenu and request.content.body etc variables.
I still think this new tag is designed after <cf_bodycontent>.
Anyway, I think that adding an attribute, lets say "clearcontent", that is
by default set to "yes", to this tag would make sense. I think it could be
useful for an example with the new <cfflush> tag.
Example: User is doing a search, you generate page header, wrap it inside
<cfsavecontent variable="header" clearcontent="no"> and also output text a
la "Please wait, searching...". Then when search finishes, you <cfflush>
and use the #header# variable to output header again (you don't have to
generate it again!) and output search results. I know that "clearcontent"
attributes isn't really needed, you can output the same #header# variable
just after ending </cfsavecontent> but it could save some processing
power, I think.
Erki
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
