I use the CFLOCATION option. To me it's more obvious what's going on.
After all, if it's a goto, I don't want to pretend it's not. It also makes
my colleagues happier. They are already a bit concerned about 25-line files
with only 3 lines of code.
As ever, the only argument I have seen for url_ files (and it's a fair
argument) is that they can be re-used and amended all in one central point.
That would be great of you were changing the goto location. I guess I would
use the url_ form in a particular case that was being a problem, but i
haven't run into one of these yet. As it is, all of my CFLOCATION jumps are
internal to the app, so I have good control over them, and they don't get
changed much.
Leeb.
>From: "Hal Helms" <[EMAIL PROTECTED]>
....
>Method A:
><cfcase value="doSomething">
> <cfinclude template="qryMyQ.cfm">
> <cflocation url="index.cfm?fuseaction=doThisNow">
></cfcase>
>
>Method B:
><cfcase value="doSomething">
> <cfinclude template="qryMyQ.cfm">
> <cfinclude template = "url_doThisNow.cfm">
></cfcase>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
