|
That’s an interesting solution, however, I’m not sure it will work in my
situation because the processes are contained within an intricate and detailed
workflow. I’m not afforded the
ability to change to a frameset for a particular transition that is part of a
bigger workflow. The scheduled task is
just a temporary patch until all of our servers have been upgraded to CFMX. Thanks - Tom -----Original Message----- What about loading your initial page in a
frameset. The inital page can load in a frame that covers 100% of
the browser's real estate while leaving a second frame invisible to the user.
You can then execute the cfhttp, parse what is returned and pass it to the
hidden frame with _javascript_. Your initial page will continue to run
after the _javascript_ executes. I ve figured out how to spawn a
second request on a different cf server. I create a schedule task with the
url to the external server with a future time stamp (say 30 seconds in the
future). The scheduled task is fired and the processing occurs on the
external server. This does not interrupt my initial line of
processing. I m not totally excited about this because there are more
moving parts which allow for greater opportunity of failure. But this
works and is only a temporary solution until all of our servers are migrated to
MX. |
- cf multiple process solution Schreck, Tom
- Re: cf multiple process solution Jeff Mayfield
- Schreck, Tom
