> OK, then you'll have to copy the results to SESSION scope and call them from > there. > > Something along the lines of: > In the first page: > <cflock scope="SESSION" timeout="10" type="exlusive"> > <cfset SESSION.myQuery = duplicate(myQuery)> > </cflock> > > Then reference it on the second page by copying to local scope. > <cflock scope="SESSION" timeout="10" type="readonly"> > <cfset myQuery = duplicate(SESSION.myQuery)> > </cflock>
Sharon, thanks for your feedback so far. But as I mentioned in a previous post, I'm in a clustered environment, so SESSION variables are out of the question -- even sticky sessions. And I don't want to resort to client variables because the WDDX packet approaches 15K and the overhead involved in returning it with *every* page call would be highly inefficient. Thanks again, Dave. ______________________________________________________________________ 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
