Re: FuseQ and XFAs

Fri, 17 May 2002 06:06:39 -0700

It sure looks like it to me, JohnF.  You build up requests by throwing entire fully-qualified fuseactions onto the Queue (FIFO).  Each fuseaction gets executed in its turn, and as far as I can see, each fuseaction's internal workings (eg XFAs) are its own business.

What I'm trying to get my head around is how to make use of the way the fuseactions are queued to be executed further on down the processing track.  That means you can't really mix up "immediate" code with FuseQ calls.  That's a little weird to me right now, because I have always mixed conditional code, etc directly into my fuseactions.  For example, this wouldn't work the way you might hope:

<cfset addToQ(person.validate)>
<cfif isValid>
  <cfset addToQ(person.insert)>
</cfif>

I'm also grappling with the concept of "making fuseactions more atomic".  Is that a good thing to do?  Do I really want to create fuseactions in order to package up a single fuse worth of code?

Obviously I'm looking forward to seeing some more examples.  I know Q was quite a hit up in the Arctic.

See ya,

LeeBB

----- Original Message -----

 

Does fuseQ still use XFAs?

Thanks,

John
==^================================================================
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
==^================================================================

Reply via email to