> Meaning faster than using ThisTag.GeneratedContent with
> custom tags.
Erki,
Has anyone at Allaire stated that explicitly? Because my assumption would be
that the real speed gain would be from using an intrinsic CFML function and
skipping the overhead associated with all custom tags... I'd be surprised to
learn that thistag.generatedcontent is, in and of itself, the bottleneck.
> I think you could as well use this new tag to do this. Example:
>
> <cfset request.content = StructNew()>
That's not exactly what I'm doing. Yeah, my cf_bodycontent defaults to
creating a request.bodycontent structure, but it also features a
"array='yes|no'" attribute. It looks like this:
<cfmodule template="bodycontent" id="foo" array="yes">
...some content...
</cfmodule>
That will generate an auto-incrementing array of content that is accessed in
a tmp_ file:
<table>
<cfloop index="x" from="1" to="#ArrayLen(request.bodycontent.foo)#">
<tr><td>#request.bodycontent.foo[x]#</td></tr>
</cfloop>
</table>
The idea is to allow someone with access to the tmp_ to add Javascript
events, CSS, or <FONT> markup to the table and fill it with dynamic content,
but never actually touch the dsp_ code that generates that content.
--
Roger
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
