I've done this both ways, and for me, I've found that storing all the form
values in client vars to be the better.
I've found the program code much easier to follow along with.
If the user's browser conks out, and the log back in with a new instance of
IE, the form values are still there.
In my app flow, I rely upon populating structures from client-var WDDX
packets, and then from structures back into WDDX. The form field defaults as
structure values thing works great with this.
I've also got plenty of forms that contain textarea boxes that can contain
more text than is allowable in a URL string. When you have to URLEncode
text, it gets way bigger in byte length, further limiting how much you can
stuff into a URL.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Reid Hankins [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, January 12, 2001 12:03 PM
> To: Fusebox
> Subject: RE: Form Validation cf_reuseform
>
> For the sake of healthy discussion, I would like to question the use of
> session or client variables for maintaining the inputs. Wouldn't it make
> more sense to just maintain the variables and pass them along?
>
> for example:
>
> user edits form and submits --> form input found invalid --> form
> inputs
> passed back to original form through url encoded attributes via
> cflocation.
>
> If their is sensitive data to pass back, you could just use a good
> encryption algorithm to encrypt the sensitive data before you send it
> across... (of course then you will need to decrypt in the form again).
>
> Reid Hankins
>
>
> -----Original Message-----
> From: McCollough, Alan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 12, 2001 8:45 AM
> To: Fusebox
> Subject: RE: Form Validation cf_reuseform
>
>
> although I don't use the cf_reuseform tag, the issue of non-JavaScript
> form
> validation is one that affects most folks...
>
> The way I handle the issue is this:
> User visits form page
> Form field value defaults are determined by checking the values within
> db-based client variables (or you could use good ol' session variables)
> User submits form.
> Form results are stored in db-based client variables (or you could use
> good
> ol' session variables), the same ones mentioned earlier
> Form validation routine is executed
> If form results are rejected, a CFLOCATION is done back to index.cfm, with
> the fuseaction being the one that invoked the form page in the first
> place.
> Since the db-based client variables are now populated with values, these
> are
> loaded up into the form, thus preserving the user's original submission.
>
> Alan McCollough
> Web Programmer
> Allaire Certified ColdFusion Developer
> Alaska Native Medical Center
{redacted}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
