> Let's say you have a form and are doing some entry into the database. Then
> you go to your next flow point which is thisfile. If you include it and
the
> user refreshes, bam you now have duplicate entries from your form because
> every include will get hit again. If you use the cflocation, no problems.
but that doesn't explain why one needs to use "url_" files. You could've as
easily thrown that cflocation into the end of the "act_" file. I think the
guy was asking for a non-stylistic rationale for using the "url_" files . To
date, i've never found one satisfactorily explained to me, it always ends up
coming down to a preferred style. And, more to the point, the reasoning
often comes down to using them post-ACT since that is typically a single
exit point for that fuse, where is DSP cases there can be very many exit
points, all using various techniques for exiting.
I'm not arguing *against* them. I'm just still waiting to be convinced as to
how whatever they do cannot be done from within the about-to-be-exited fuse.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
