Alan,
Although your plan is well thoughout, have you considered the performance
hit to forcing CF Server to parse every character of every template? Maybe
the performance hit wouldn't be all that bad, but I would need to see some
evidence before I was convinced. I will say that your ideas have merit and
should be examined. Maybe it just seems too easy to be true. Anyone out
there want to do some experiments?
Jason
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 30, 2000 9:14 AM
To: Fusebox
Subject: RE: <cfoutput>#request.variable#<cfoutput>
I'm curious about this one... I mean, I'm thinking, this is an issue that I
do think could be considered as part of the Fusebox methodology.
I see four possibilities here:
1: Apply CFOUTPUTs tersly, only around specific portions of code that need
it
2: Apply CFOUTPUTs around large blocks of code, which may or may not need it
everywhere
3: Apply CFOUTPUTs around the entire template, with only CFMAILs and other
anti-CFOUTPUT functions being left out.
4: Apply CFOUTPUTs at the index.cfm level, and explicitly escape out
anti-CFOUTPUT tags by starting with </CFOUTPUT> and ending with <CFOUTPUT>
to restart the CFOUTPUT string
Now, lets think of it like this.... here is an idea, so I'm lookin' for
input, advice, what-have-you...
A Proposal For Structuring a Fusebox App So That Everything Is Implicitly
CFOUTPUTted
PART 1: The Index.cfm file
You take your index.cfm, and make it look like this...
<CFOUTPUT>
<CFSWITCH ....>
{all the CFCASE statements for fuseactions}
</CFSWITCH>
</CFOUTPUT>
PART 2: Working with Query Recordsets
Tell yourself and anybody concerned that they are to use <CFLOOP QUERY=..>
instead of <CFOUTPUT QUERY=..>
PART 3: Dealing with anti-CFOUTPUT code, such as CFMAIL
Encapsulate all code by STARTING with a </CFOUTPUT> and ENDING with a
<CFOUTPUT> to restore the CFOUTPUT nest.
The End...
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 29, 2000 5:46 PM
> To: Fusebox
> Subject: RE: <cfoutput>#request.variable#<cfoutput>
>
> ... Also, just be aware that there is a performance
> penalty with wrapping the whole page in cfoutputs.
> {redacted}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
