This way is safe because of the non-recursive nature of the Fusebox XML grammar (i.e. it's impossible to call the original fuseaction twice in the same request). That's a subtle point, however, so I'd vote for more explicit way: use a per-request flag.
cheers, barneyb On 10/31/06, Peter Boughton <[EMAIL PROTECTED]> wrote: > Ah, that's an idea! > I can compare originalFuseaction to currentFuseaction, and that will tell me > whether its the first FA or not? > If the two match then I run everything, otherwise I do nothing. > *crosses fingers* > > >That's what prefuseaction does. Runs before every fuseaction. You > >could use some conditional logic in the prefuseaction to only run > >once, but that's kind of hackish. Or you could use a global > >preprocess which would give you what you want, but unless it's truly > >global, it's kind of hackish because you'll need a conditional to > >constrain it to the circuit. A better solution (in my view) is to > >differentiate your public fuseactions from your private fuseactions, > >and then use a prefuseaction block that only runs on public > >fuseactions. That should meet the need, and can be as simple as > >prefixing your private fuseactions with an underscore, or as complex > >as using a separate circuit for private stuff. > > > >cheers, > >barneyb > > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:258598 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
