|
Hi Mike,
Generally in Fusebox, we have a distinction between
low-level, private, atomic functions (called Fuses) and higher-level, public
functions (called FuseActions).
We use <cfinclude> to call the low-level Fuses, and
<cfmodule> to call entire high-level FuseActions.
(There is also a new, quasi-proprietary, extension to the
FB3 framework, called FuseQ, that's getting a fair bit of discussion at the
moment. It provides an alternative method for invoking entire
FuseActions. Watch this space to see if it becomes
standardised.)
Does that make sense?
Thanks,
LeeBB
----- Original Message -----
==^================================================================ 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 ==^================================================================ |
- CFMODULE vs CFINCLUDE Mike
- Re: CFMODULE vs CFINCLUDE Lee Borkman
- Re: CFMODULE vs CFINCLUDE Mike
- RE: CFMODULE vs CFINCLUDE hal helms
- Re: CFMODULE vs CFINCLUDE Mike
- RE: CFMODULE vs CFINCLUDE Xavi
- Re: CFMODULE vs CFINCLUDE Lee Borkman
- Re: CFMODULE vs CFINCLUDE John Quarto-vonTivadar
- RE: CFMODULE vs CFINCLUDE hal helms
- Re: CFMODULE vs CFINCLUDE Lee Borkman
- Re: CFMODULE vs CFINCLUDE Evan Wilders
- Re: CFMODULE vs CFINCLUDE Lee Borkman
