i think it's important to also keep in mind that even when things are nested
several fuses deep, that that is by the architect's choice....you can as
easily make everything be nested one deep simply by expanding the
top-level's Circuits.cfm file.
it took a few days for that to sink in with me, so that is why I'm offering
the thought up.
Also, I'd dare to say that if one's app is multiply-multiply nested then
perhaps there's a chance that it is too complexly nested? (not that it is,
but you should at least consider the possibility). Sometimes being too
general, although it looks good in theory, results in a nightmare,
particularly if you get hit by a bus and some other schmuck has to take over
your code. That's one of the reasons Hal did NOT make the Circuits.cfm
inherit all the sub-fuseboxes beneath it automatically.
> See .. it's the overhead I don't get. I'm developing a site that's nested
a
> few layers deep. All I do to accomplish this smoothly is this:
>
> Every circuit has it's own app_globals
> Each app_globals includes the app_globals from the circuit directly above
> them.
> The index.cfm in each circuit controls the flow as normal.
>
> I now have an app that's nested 4 circuits deep with no problems. Every
> circuit can stand on its own or be used in any application. The only
files
> that might need to be changed are the app_locals and maybe the app_globals
> if a circuit becomes the root.
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
