Having just one circuits.cfm defeats the purpose of Hal's XFB architecture.
The idea is that you can run any of the circuits as independent
applications, or as part of a higher level application. To do this, each
circuit app needs to know all its sub-cicuits. This is fabulous for
developing sub-apps, testing them , and then plugging them in
In truth, the possibility of naming conflicts is no great problem, as long
as you have some means of discovering and eliminating them (see my
CF_AddCircuits blurb).
We all learn, you mess with Hal's ideas at your peril ;-)
LBB.
-----Original Message-----
From: Amir Razmjou [mailto:[EMAIL PROTECTED]]
I think that one solution is
1. Just having one Circuits.cfm in home application and including it in
app_globals.cfm this eliminates naming conflicts.
....
IMPORTANT NOTICE:
This e-mail and any attachment to it is intended only to be read or used by
the named addressee. It is confidential and may contain legally privileged
information. No confidentiality or privilege is waived or lost by any
mistaken transmission to you. If you receive this e-mail in error, please
immediately delete it from your system and notify the sender. You must not
disclose, copy or use any part of this e-mail if you are not the intended
recipient. The RTA is not responsible for any unauthorised alterations to
this e-mail or attachment to it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
