Why not? I've done this myself a few times. THe reason? I like fuseactions
that have somewhat descriptive titles such as "init_user_vars", "logout",
"clearvars", etc. There are times when for purely stylistic reasons, I want
to use a different fuseaction name, although the actual functions performed
are identical to an existing fuseaction. I didn't see any bad performance
hit, and for me at least, it left me with an easy to read fuseaction name,
and only a single set of actions to debug. That's pretty good reusability,
I'd say.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
{redacted}
> Case FA1:
> Display something
> Case FA2:
> Redirect to Case FA1
>
> Certainly, one would never use this approach; one would simply create the
> case
> for FA1 and be done with it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
