Re: CF Page Won't Stop Executing

On Wednesday 19 April 2006 14:43, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Am I in the middle of a brain-burp, or is it not in fact the case that CF used to stop executing the current page if the user hit their stop button Don't recall CF6 ever being able to do that. -- Tom Chiverton

Re: CF Page Won't Stop Executing

I'm not sure about that either. As for stopping a long running request, use the CF Admin option to stop a page running longer than x seconds. There's also Fusion Reactor or SeeFusion, which can both selectively terminate running CF requests. On 4/19/06, Thomas Chiverton [EMAIL PROTECTED] wrote:

Re: CF Page Won't Stop Executing

Thanks, I was afraid that I was working with old recollections. I've been looking at both FusionReactor and SeeFusion, so now it's time to move forward. I like FusionReactor better because it handle all of the installation itself. SeeFusion is nice because it shows more info on queries, but

RE: CF Page Won't Stop Executing

Reed, Am I in the middle of a brain-burp, or is it not in fact the case that CF used to stop executing the current page if the user hit their stop button and opened a new CF page? I have pages that continue to execute even after the user hits STOP and REFRESH - so now I have a couple of copies

Re: CF Page Won't Stop Executing

I realize that the STOP alone doesn't have an effect on the currently executing page - but didn't CF (pre-MX I guess) used to stop the current request when it saw a new request from the same browser? I'm pretty sure that I used to be able to stop runnaway pages by hitting STOP and then

Re: CF Page Won't Stop Executing

On Wednesday 19 April 2006 15:34, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: So I guess the bottom line is that with any of the CFMX versions there is no protection from users getting impatient waiting for a page that legitimately takes a few seconds to process, and repeatedly hit REFRESH?

Re: CF Page Won't Stop Executing

On Wednesday 19 April 2006 15:45, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: that I used to be able to stop runnaway pages by hitting STOP and then browsing to another CF page - but maybe I'm just halucinating. And how did CF know the difference between that, and a multi-frame'd page ? --

RE: CF Page Won't Stop Executing

I realize that the STOP alone doesn't have an effect on the currently executing page - but didn't CF (pre-MX I guess) used to stop the current request when it saw a new request from the same browser? I'm pretty sure that I used to be able to stop runnaway pages by hitting STOP and then browsing

RE: CF Page Won't Stop Executing

Hitting the stop button previously only stopped your browser interacting with the server. It still runs any process it was told to before. Eric J. Hoffman Managing Partner 2081 Industrial Blvd StillwaterMN55082 mail: [EMAIL

Re: CF Page Won't Stop Executing

On 4/19/06, Dan G. Switzer, II [EMAIL PROTECTED] wrote: The one exception to CF killing a thread when a connections is closed might be if you were using CFFLUSH to dump the output stream to the browser. It's Seems to be hit and miss. I've got a long running page that uses cfflush, sometimes

RE: CF Page Won't Stop Executing

Denny, Seems to be hit and miss. I've got a long running page that uses cfflush, sometimes it stops running (when browser go away), mostly it doesn't. Maybe the confusion is in the socketWhatNot error or whatever, that one Thanks for the information. That's pretty much what I figured, but that