On the surface it looks as though the RequestTimeout functionality in CFMX is woefully broken. Have been holding out from the beginning of the month in hope that the "updater" might have addressed this issue, but alas. So here's some info on trying to get this thing to work.
The docs say I should be doing something like...
<cfset someVariable = "300">
<cfsetting RequestTimeout = "#someVariable#">
To extend the timeout of a page. The exact example suggests putting in a value for URL.RequestTimeOut to simulate CF5 behaviour. For example:
<cfparam name="RequestTimeout" default="35">
<cfsetting RequestTimeout = "#URL.RequestTimeout#">
The problem is CFMX throws an error if the RequestTimeOut attribute of CFSETTING is a variable of *any* kind. It seems as though a runtime evaluation of the variables value is just not possible, as the error thrown is a compiler error.
For example, this works:
<cfsetting RequestTimeout = "300">
But this does not:
<cfset somevariable = "300">
<cfsetting RequestTimeout = "#someVariable#">
At the very least this is an error in the documentation. And certainly something that people should be aware of migrating applications from CF5 where you may have made use of the RequestTimeOut URL parameter for long running pages.
Posted by modius at 12:22 PM | Permalink
Trackback: http://blog.daemon.com.au/cgi-bin/dmblog/mt-tb.cgi/46
Since installing Updater 2, this behaviour has reversed (on our servers, at least):
<cfset somevariable = "300">
<cfsetting RequestTimeout = "#someVariable#">
now works, and
<cfsetting RequestTimeout = "300">
doesn't!
Posted by: Tom Dyson on December 19, 2002 11:02 PM