> 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?
Clint,
I'm assuming that you're using client variables and don't want to absorb the
registry/DB hit of repeatedly storing and retrieving the variables in
question.
With that assumption in mind, I might try having the fuse call the fusebox
itself as a custom tag, rather than redirecting. So instead of:
<cfcase value="myaction">
<cfinclude template="act_dothis.cfm">
<cflocation url="index.cfm?fuseaction=finishedthis&myvar1=a&myvar2=b">
</cfcase>
....you'd have:
<cfcase value="myaction">
<cfinclude template="act_dothis.cfm">
<cfmodule template="index.cfm" fuseaction="finishedthis" myvar1="a"
myvar2="b">
</cfcase>
However, you mentioned that you're not working with "real Fusebox", which
implies it may not be possible for the application to call itself as a
custom tag. In which case, I'm stumped. [g]
--
Roger
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
