I have never seen any examples of saving multiple form variables in WDDX. Do you add all form variables or the form name into the CFWDDX tag? ..david -----Original Message----- From: Steve Nelson [mailto:[EMAIL PROTECTED]] Sent: 04 May 2001 1:28 AM To: Fusebox Subject: Re: Managing program flow I think it's actually more elegant. Nothing is written to the server until it's finalized. One thing I've done in the past is write all of the form fields to a WDDX packet and pass that as a hidden form field instead of a client variable. No database access at all. Then you can have multiple page forms and only pass a single variable from page to page. It makes the variable passing very easy. Then when the user is finished, save it all to the db. This takes load off of your server and more importantly it doesn't leave a lot of dangling data. Steve Nelson Erik Voldengen wrote: > > Back in the old days, I just populated all previous form field values > into hidden form variables of the next form. > > For example, step one took name, address. Step 2 (another fuse) > checked for those values, put them in hidden form variables (there > is a nice custom tag in the dev-x for this), and took all step 2 > information. Step three, again, populated all existing form variables > into hidden fields, and took further info....etc etc etc. > > I did it to avoid using session variables, and to avoid making a write > to the DB until the user actually committed to the purchase by entering > their cc number. It seemed to work pretty good, and has been for a > couple years. > > Not the most elegant, but I wonder if this approach is any less/more > expensive than writting client variables to do the job. I would say > less. Hmmm. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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
