No good, the templates that require extra time would also inherit the
timeout.  I could use some cfif logic to use the cfsetting on all pages
except a couple listed, i.e....

<cfif CGI.SCRIPT_NAME IS NOT ".....">
  <cfsetting .....>
</cfif>

But really I want the control to be on the templates for the long pages.
If...
<cfsetting requesttimeout="0"> worked as a disable that would be perfect
because I could set a global 30 seconds in the administrator (or
application.cfm) then just disable it on the few, but it doesn't.  I am
reluctant to use <cfsetting requesttimeout="20000"> as I really want to
disable the timeout, not just extend it.

--
Jay

> -----Original Message-----
> From: Robertson-Ravo, Neil (RX)
> [mailto:[EMAIL PROTECTED]
> Sent: 23 September 2004 11:59
> To: CF-Talk
> Subject: RE: Disabling request timeouts
>
> Just add <cfsetting...> to your Application.cfm file and all
> pages will inherit the timeout if required.
>
>  
>
>    _____  
>
> From: James Smith [mailto:[EMAIL PROTECTED]
> Sent: 23 September 2004 11:55
> To: CF-Talk
> Subject: Disabling request timeouts
>
>  
>
> I want to have a global request timeout on the server of
> about 30 seconds but there are a few (3 so far) templates
> that I need to be able to run for up to 30 minutes.  Is there
> no way to disable the timeout for an individual template or
> am I going to have to disable it in the administrator and
> then enable it one page at a time with the cfsetting tag?
>
> --
> James Smith
> [EMAIL PROTECTED]
>
>    _____  
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to