I find it helpful to think of XFB-based nesting in terms of what I call the Two-
Tier Multiple Circuit (TTMC) model: The upper tier is the master app, with
circuits in the lower tier. The tiers are represented in the fuseaction by the
parts separated by a period; "cart.retotalCart" is a fuseaction that asks the
upper tier to pass along to circuit "cart" a fuseaction of "retotalCart".
The beauty of XFB is that this two-tier approach becomes like a sliding window
when you have multiple levels nested. At any time, the fusebox file at any
level is only concerned with doing one of two things: either calling a
fuseaction in its own level (in which case the fuseaction has no periods in it)
or sending the fuseaction to a circuit in the tier below (in which case the
fuseaction has one or more periods in it). By following this logic, you can
think of even the most deeply nested applications in terms of a bunch of two-
tier relationships. This prevents the confusion inherent to genealogy ("but is
that my parent, grandparent, great-grandparent, first cousin twice removed...")
by recognizing that, fundamentally, every individual (circuit) can be only one
of two things: a child, or both a child and a parent. In the first case, you
can only do one thing: process your own fuseactions. In the second case, you
can only do one of two things: process your own fuseactions or pass the
request along to one of your children.
So the key to grokking XFB is to avoid thinking it's more complex than it
really is.
It might help you to download Fuseminder from www.grokfusebox.com and use it to
build the sample framework. This is a simplified two-tier application, without
the XFB niceties tacked on. You might get a better understanding of how the
TTMC model works, and from there a better idea of what XFB is about.
- Jeff
[EMAIL PROTECTED]
On 29 Mar 2001, at 10:48, Sneid wrote:
>
> I'm a newbie to extended Fusebox - have already read the Extended 101 from
> Hal and some other docs.
> Does someone have a more concrete example of nesting circuits application
> other than the " grandfather/father/son model ".
> Some in-depth explanations of the respective ciruits will be most welcomed.
>
>
> Thanks
> Sneid
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
