Yup...couldn't agree more. And when I run into the problem I find a better
way to break up the information: store it to a data base and only pass id
values, think about serialzing the data and doing the same to a temporary
database using session information to retrieve it, break up your pages more
so there is not as much information on any 1 given page but instead use a
temporary storage facility and use "wizard" like interfaces to move back and
forth. I realize you are right but would need to be convinced that there is
a more productive method that will still allow me to move easily from
circuit to circuit. Provide a better example and I am sure I will be a
cheap date.
-----Original Message-----
From: Patrick McElhaney [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 09, 2001 4:25 PM
To: Fusebox
Subject: RE: Taking the fuses out of the fusebox.
> The additional request is a drag to be sure, but if you need to retain any
> attribute settings, pass them through in the url_ redirector.
But what if I have a lot of attribute settings, or one of those settings
is a long string? And what if I don't want to have a bunch of extra code to
keep up with?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
