> How about having the top frame submit to itself. All processing is done
> normally and in the end query is set to a session variable with a unique
> name. After that you add 1 javascript function using cfhtmlhead. The
> function looks something like:
> function reloadBottom() {
> top.frames[1].location = 'blahblah.cfm?fromcache=#uniquename#';
> }
>
> On the resulting request you just grab the query from the session scope
> based on the unique name. If it is large don't forget to delete the
> session variable afterwards.
>
The problem with that is two-fold. First, I'm in a clustered environment, so
I can't use session variables. Second, I am receiving a 15K WDDX packet
back from a Python server that I am de-serializing. So setting the packet to
a client variable isn't reasonable either. The resulting variable would be
huge and a burden on the CF server because it would inherently be retrieved
on every CF call within the application.
Also, as a rule of thumb, I always have my forms submit to themselves. This
allows me to have self-contained forms which are easy to re-use and
maintain.
Regards,
Dave.
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
