I use db-driven client variables in my app.
What I do is take form field values, serialize 'em into a WDDX packet, and
store that packet in a client variable. Then, when I CFLOCATE to a different
fuseaction, I deserialize the packet back into the form. I don't pass
anything in the URL of the CFLOCATE except for the fuseaction var.
Which brings up a philosophical point; I try to keep as little as possible
in the URL string. In the case of a CFLOCATE, I just tack on
"fuseaction=...."
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Clint Tillerson [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, January 18, 2001 9:00 AM
> To: Fusebox
> Subject: CFLOCATION and form variables
>
> First, I'm sure this has been addressed, but a search of the
> archives didn't clear it up for me.
>
> I'm slowly incorporating some of the fusebox techniques into a few
> systems I maintain or are in development. (I wish I had the
> opportunity to develop a real fusebox site from scratch. Maybe in
> the near future.)
>
> I'm curious how others address this issue. Fusebox makes heavy
> use of the CFLOCATION tag. Say I want to insert data into a table
> from a form the user just submitted, then redirect the user to
> another template. The only way I have access to the form variables
> after the insert is to pass them all via the URL in the CFLOCATION
> tag. Is there another way to handle this? Some of our systems
> track a lot of variables throughout a user session. For most
> variables, the values are user defined and change frequently. Many
> of these variables are variables used for data filtering set by the
> user that I need to hold on to from page to page. To keep URLs
> clean, I try to pass them from page to page via forms. In some
> cases I use a routine to serialize them into a WDDX packet then
> deserialize them on the subsequent page. This keeps things clean
> and neat only one form variable to deal with). CFLOCATION
> prevents me from doing this, right?
>
> Of course, I use session/client variables to hold static values
> (variables that are generally set only once during a session).
>
>
> ------------------------------------
> Clint R. Tillerson
> Meteorologist/Programmer
> Pacific Environmental Services, Inc.
> 5001 South Miami Blvd.
> PO Box 12077
> RTP, NC 27709
> (919) 941-0333
> Fax: (919) 941-0234
> ------------------------------------
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
