That brings about another question... Since we use app_globals, and don't
have application.cfm's - what's the penalty for not having an
application.cfm?  Does CF look recursively up the tree EVERY time a call to
a fusebox app is made?

I guess we could make a simple application.cfm, that doesn't do anything,
but at least CF doesn't have to go looking around for something that ain't
there.

Thoughts?

-Bill
www.brainbox.tv

----- Original Message -----
From: "Greg Zentkovich" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Monday, May 14, 2001 3:41 PM
Subject: application.cfm Q


> I needed some clarification...
>
> Are multiple application.cfm's are allowed/possible in a directory
> structure? Meaning, one for each application created.
>
> Example:
> If I have a sub-directory called /workorders and I place a application.cfm
> file in there...
> e.g. <cfapplication name="workorders" clientmanagement="Yes" ... >
>
> Then I have another sub-directory called /finance and again I place it's
own
> application.cfm in there...
> e.g. <cfapplication name="finance" clientmanagement="Yes" ... >
>
> They shouldn't conflict with each other because their cf_application names
> are different, so variables attached to them are attached to a particular
> cf_application name. Is this correct?
>
> So this scenario is possible?
> /wwwroot (application.cfm - cf_app name=main)
>  |_ /workorders (application.cfm - cf_app name=workorders)
>  |_ /finance (application.cfm - cf_app name=finance)
>
> The reason I'm asking is because some of us only have access to the
> directory we are working on and if we wanted to use applicaton.cfm with
our
> fusebox app I wanted to make sure we wouldn't interfere with other
people's
> apps...
>
> TIA,
>
> Greg
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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

Reply via email to