To be honest, the the suggestion to NOT use application.cfm was an old one,
and yes it was because application does not get called when a fusebox is
inccluded as a custom tag. There has been many arguements recently for
using application.cfm, one real good one is for security reasons. For the
book however we decided to stick with the old way, for two reasons
1) let the newbies learn when and when not to use application.cfm
2) let the arguements for using application.cfm formulate a little more
Craig
-----Original Message-----
From: Matt Wisdom [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 04, 2000 12:56 PM
To: Fusebox
Subject: Fusebook
I purchased and am reading through the fusebook, and I'm wondering if I have
the correct interpretation of one of its recommendations:
1) don't use application.cfm
2) use app_globals.cfm
3) cfinclude app_globals.cfm in your index.cfm file
4) use request scope to access those variables in code that is accessed
through cfincludes and custom tags
The problem (and I assume quite a known one) I had previously was that
application scope variables could be read by cfincludes, but not by custom
tags since they are in their own memory space. This appears to be the reason
application.cfm is recommended against, and the purpose of using the request
scope -- that it works for both cfincludes and custom tags. Is this correct?
If so, what is the magic behind the request scope, and how much performance
does it cost? I've got 50 application-wide variables, and I hate to set them
every page request.
Thanks,
Matt
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
