> I think we all agree that the only way out of a dsp_file is
> through an exit
> point embedded in that file...
Nat,
Not necessarily. One might choose to relocate out of a dsp_ if the file in
question discovers some sort of data-related problem... for example, a URL
hacker has decided to do something out-of-bounds with a variable or two.
And of course, on my current project, I'm using a modified cf_bodycontent in
conjunction with "tmp_" files to provide for easy end-user customization.
All the programmatic content is generated in a dsp_, but it actually gets
delivered to the user-agent via a tmp_.
In both situations (admittedly, the second is a special case), a dsp_ does
not mean the end of the fuse.
> This final code example and techinque does not use url_files,
> allows maximum
> reuse of action files, and still provides index.cfm as a roadmap to the
> application.
It also seems to introduce unnecessary duplication of conditional code that
would be better suited for a url_ file. [g]
--
Roger
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
