Hi Avi,
I'll jump in here on this one. You are misusing the "app_Globals" file.
There should be only ONE app_Globals file in your directory structure --
usually in the root.
Then, each circuit application (subfolder) should contain an "app_Locals"
file which then directly calls the "app_Globals" file in the root of your
APPLICATION.
This way, in ANY given circuit application, the fusebox calls the app_locals
file which contains constants and rules for THAT circuit application, and
then calls the "app_Globals" file, which contains the constants and rules
for the entire application.
Marc Funaro
-----Original Message-----
From: Avi Flax [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 9:47 AM
To: Fusebox
Subject: Multiple app_globals includes?
I've had this question for a little while now and I'm tired of waiting for
the book or a FAQ. So here goes: When I have multiple nested FuseBox apps
(I call them FuseApps), how do you deal with a situation where you need
certain code to execute with every single page access, no matter where? I
got the impression from the FuseBox spec that we want to avoid using
Application.cfm so that we can use our FuseApps as Modules (which I still
haven't seen the need to do) - so fine, I include an app_globals in the
root of each app (included by the FuseBox (index.cfm)) . I have each
app_globals file in each nested directory including the one in the
directory above it:
So:
root/index.cfm includes root/app_globals.cfm
root/products/index.cfm includes products/app_globals.cfm, which includes
root/app_globals.cfm
root/products/wheels/index.cfm includes app_globals.cfm, which includes
products/app_globals.cfm, which includes root/app_globals.cfm
End result of all of this is that every time I access a page in the deepest
level, 12-15 files are being processed by the CF Server! This has GOT to be
a performance hit, and not the most efficient way to do this.... Can't we
just use application.cfm.... or can someone demonstrate why it is
preferable not to?
While I am writing, is it appropriate to move control of the browser from
one app to a subapp using CFLOCATION, or are we supposed to stick to using
CFINCLUDE every time, no matter what, and have the root FuseBox control
everything - I am not sure, but I think I noticed the eBags site using
CFLOCATION to move to subdirectories.
Thanks!
Avi
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
