Fusebox commonly uses cflocation in its redirector files (url_ files) and it
is not required really. The whole point of these files is to not only help
move from one circuit to another, but also to help prevent refresh message
issues. You can pass your query string with cflocation or if it is too
large a set of parameters, you could break the model a little and use the
url_ file to create a form that traps your current attributes you need on
the next page and force a submit to a new circuit to carry those values
along. But if you are jumping circuits, this can be problematic so I am not
sure I could recommend it. Cookies would be a simple and happy solution or
WDDX to serialize your data to make a stream of information that will travel
much easier than a huge (an potentially problematic) url string.
Mike Craig
Its a Fusebox World
-----Original Message-----
From: Clint Tillerson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 1:00 PM
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
