Avi,
This ain't religion...
With nested fusebox apps the original spec calls for having an app_globals
in the root of the Application (this is where CFAPPLICATION gets called! )
and an app_locals in any lower down level which includes the root
app_globals.
So at any level only two files are being included.
About CFLOCATION vs. CFINCLUDE, again not written in stone, mostly depends
on where do you want control to return to from links on the page - back to
the root or directly to the circuit app.
I prefer CFLOCATION where a clear division can me made as it makes the
index.cfm's smaller and easier to manage. Though for the user there is a
performance penalty as there are two trips to the server... (lucky it's not
a big deal with intranet sites :).
Hope this helped clear things up,
Noam
----------
From: Avi Flax [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, 05 October 2000 15:47
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.
