Yvette, wouldn't a simple solution be to store the data in a session
variable then pick it up on the receiving end? You can add a switch
to the querystring if needed.
First template:
<cflock scope="session" timeout="30" type="exclusive">
<cfset session.mydata = some_complex_structure>
</cflock>
<CFLOCATION url="template.cfm?readdata=1" addtoken="yes">
Second template:
<cflock scope="session" timeout="30" type="readonly">
<CFIF isDefined('url.readdata') and isdefined('session.mydata')>
<cfset some_complex_structure = session.mydata>
</CFIF>
</cflock>
--
Bud Schneehagen - Tropical Web Creations
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
ColdFusion Solutions / eCommerce Development
[EMAIL PROTECTED]
http://www.twcreations.com/
954.721.3452
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
