Interesting. Sounds kind of like a session bean in Java. What
do you do when the user has multiple browser windows open? For
example, say I have a four-step wizard to edit Widgets. I open
the wizard for Widget A in one browser window, go through
the first two steps, and then start with Widget B in a new
window and do the first step. Then I go back to Widget A. Does
it take on some of the properties of Widget B, or lose what I
entered in the first two steps?
I can see how one could get around this, but I don't want to
reinvent J2EE.
Still don't have a better way, but I think I'm on the right
track. I think the best bet is if we can figure out a way to
keep changing fuseactions within a single transaction until we have
something to present to the user.
How about this?
<cfset attributes.nextfuseaction = "">
<cfloop condition="#len(attributes.fuseaction)#">
<cfswitch expression="#attributes.fuseaction#">
<cfcase value="form">
<cfinclude template="dsp_form.cfm">
</cfcase>
<cfcase value="update">
<cfinclude template="act_update.cfm">
<cfif len(attributes.errors)>
<cfset attributes.nextfuseaction="form">
<cfelse>
<cfset attributes.nextfuseaction="confirm">
</cfif>
</cfcase>
<cfcase value="confirm">
<cfinclude template="dsp_thankyou.cfm">
</cfcase>
</cfswitch>
<cfset attributes.fuseaction = attributes.nextfuseaction>
</cfloop>
Patrick
> 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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
