> A) The only thing that references fusefiles is the switch in the same
> circuit.
that's correct, and you'll notice that with FuseQ you reference other
fuseACTIONS not other fuses
<cfset AddToQ ( 'queries.qListStates' )>
>
> B) The only place that fuseactions are referenced explicitly is in a
> switch file (either local circuit or remote).
> Aren't XFA's essential to implementing that principle ?
and that would continue to be that way: you'd set an XFA in either a
fbx_settings file or in the switch file.
THe thing to keep in mind with FuseQ is that you're still in the same page
request to the server all the way through the FuseQ. So any variable you've
created along the way remains available. It's NOT like calling a bunch of
CFMODULEs
>
> Andy.
>
>
>
>
>
> Brian Kotek wrote:
> > John, I'm pretty sure that XFA's are independent of which core you use.
> >
> > They're more of a best practice thing than a Fusebox API thing. Nothing
> >
> > in the core will scold you if you aren't using XFA's, because they are
> > just variables that get evaluated to Fuseactions at runtime. XFA's just
> >
> > make your life a lot easier when it comes to reusing code or increasing
> > your fuses' flexibility (as I'm sure you know). So I'm quite sure that
> > you can XFA to your hearts content.
> >
>
>
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
