This brings me to another question. How do you do data validation? Do you
check for correctly formatted data (coming from URL and FORM and copied to
attributes) in every fuse or do you have only first fuse that cleans up
(makes sure its numeric etc) the info coming from user and other fuses in
the same fuseaction trust the data?
VERSION 1:
switch
case some_fuseaction
include qry_getSomething.cfm // checks incoming vars
include qry_getSomethingElse.cfm // checks incoming vars
include dsp_something // checks incoming vars
/case
...
/switch
VERSION 2:
switch
case some_fuseaction
include err_checkUserInput.cfm // checks incoming vars
include qry_getSomething.cfm // trusts incoming vars
include qry_getSomethingElse.cfm // trusts incoming vars
include dsp_something // trusts incoming vars
/case
...
/switch
-erki
----- Original Message -----
From: "Steve Nelson" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Thursday, May 03, 2001 7:09 PM
Subject: Re: Managing program flow
> well... they attributes at the top level can be modified by user if you
> use the <formurl2attributes> tag, because attributes are essentially the
> same thing as the URL and form scopes.
>
> Does that make sense?
>
> Steve
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
