Patrick that is a awful example! :) You're using the your fusebox to
substitute for proper query caching. !
(also see below)
>
> <cfcase value="aDecentExample">
> <cfinclude template="qry_getAGoodReason.cfm">
> <cfinclude template="act_ConvinceJQvT.cfm"> <!--- uses
> qry_getAGoodReason.cfm --->
> <cfinclude template="dsp_example.cfm"> <!--- also uses
> qry_getAGoodReason.cfm --->
> </cfcase>
>
it looks to me like you're doing two things with one fuse. you could have
easily written this as
<cfcase value="convincePMcE">
<cfset XFA.onExit = "displayexample">
<cfinclude template="act_convincePMcE.cmf">
<!--- some people may choose to put another cfinclude to a "url_" file
here; XFB lets the XFA's handle it --->
</cfcase>
<cfcase value="displayexample">
<cfinclude template="dsp_example.cfm">
</cfcase>
one thing I'm noticing is that the folks who are pro "include it in the
fusebox!" are also tending to be the ones not using XFA's. is the
correlation cause-and-effect? Are people not using XFA's because they're not
properly understood, or because they're consciously thinking that XFA's are
sequentialy related to XFB jsut because of the lettering?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
