This is from the documentation http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/tags-pc6.htm -------------------------------------------------------------- The cfsetting requestTimeout attribute replaces the use of requestTmeOut within a URL. To enforce a page timeout, detect the URL variable and use code such as the following to change the page timeout:
<cfsetting RequestTimeout = "#URL.RequestTimeout#"> -------------------------------------------------------------- Also this from the migration documentation, under the "Request Variable" section http://livedocs.macromedia.com/coldfusion/6/Migrating_ColdFusion_5_Applicati ons/cf_migration_guide10.htm -------------------------------------------------------------- ColdFusion MX no longer supports the RequestTimeout attribute in the URL. For pages expecting the RequestTimeout attribute in the URL, add the following tag: <cfsetting RequestTimeout = "#URL.RequestTimeout#"> -------------------------------------------------------------- So i would think that it does not work anymore. Now I guess the next question is what is the macromedia definition of "Not Supported"? The service factory stuff is said to be "not supported" but it works, bit the way the above reads, i get the impression that "not supported" mean it doesnt work anymore. Eitherway, the documentation states to not use the ?requesttimeout=500 method of overwritting the timeout value of a page, which means that the answer they have said is correct is NOT correct. Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Barry Beattie Sent: Monday, September 13, 2004 11:47 AM To: CFAussie Mailing List Subject: [cfaussie] Re: requestTimeout >> so by saying that, your saying that if it works then its correct? >> so not locking shared scope variables is correct cause it works? there's a big diff between these 2, Steve. you're comparing apples to oranges. if it works: just a yes/no. (timeout via URL) if you should: maybe. (locking shared scopes) for the cfbuster question: if it works, it works. end of story. >> Which of the following *can* you add to - straight yes/no stuff: not >> Which of the following *can* you AND SHOULD YOU add to... - which is what you're impling by comparing the timeout Q to locking shared scopes. >> so if CFBuster says its correct but the CFMX Docs say its incorrect then its correct. the bottom line is "what is the truth"? does ANY of the answers to the Q work? if so, bingo. question can be answered. so what was the answer, again? cheers barry.b -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Onnis Sent: Monday, 13 September 2004 11:29 AM To: CFAussie Mailing List Subject: [cfaussie] Re: requestTimeout so by saying that, your saying that if it works then its correct? so not locking shared scope variables is correct cause it works? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of M@ Bourke Sent: Monday, September 13, 2004 10:31 AM To: CFAussie Mailing List Subject: [cfaussie] Re: requestTimeout "The reason I ask is that I downloaded the trial of CFBUSTER and one of the questions is as follows" CFMX exam buster goes by what works in coldfusion and not by what the cf documentation says works. so if CFBuster says its correct but the CFMX Docs say its incorrect then its correct. CFbuster is always right :) --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
