Skip to main content

ColdFusion 10: Disabling request timeout

A very quick post on disabling timeout for the requests. You can now set the requesttimeout to zero in cfsetting tag i.e.

<cfsetting requesttimeout=0>

This setting is particularly useful if the server is executing a task which might take longer than the usual or the response time is not known in advance.

<cfsetting requesttimeout="0"> <cfset count = 0> <cfloop condition="true"> <cfthread action="sleep" duration="1000" /> <cfoutput>#++count#</cfoutput> <cfflush> </cfloop>

The above code would run indefinitely and the request timed out page will not be shown.
Labels:

Comments

  1. Oğuz Demirkapı ☮March 6, 2012 at 11:29 PM

    We were settings as something like 99999999. So why did you created this one? Who may need an endless wait? :)

    ReplyDelete
  2. Sam FarmerMarch 6, 2012 at 11:54 PM

    Nice addition. Is there a script version as well?

    ReplyDelete
  3. Sagar GanatraMarch 7, 2012 at 12:19 AM

    Oh yes!! In cfscript you can have 'setting requestimeout=0'

    ReplyDelete
  4. Sagar GanatraMarch 7, 2012 at 12:21 AM

    setting requesttimeout to a very high value is a hack and not a clean way to disable the timeout. Some applications may need endless wait. Say your application is reading Twitter stream at regular intervals and flushes out any available data to the client.

    ReplyDelete
  5. Sam FarmerMarch 7, 2012 at 1:29 AM

    Awesome. Is that true for all setting attributes?

    ReplyDelete
  6. NickMarch 7, 2012 at 2:38 AM

    In cf9, requesttimeout is not respected on a processing page containing cfthread.  Did they fix this on cf10?

    ReplyDelete
  7. Sagar GanatraMarch 7, 2012 at 9:59 AM

    Yes. setting enablecfoutputonly="true" requesttimeout="0" showdebugoutput="yes"; is supported.

    ReplyDelete
  8. Sagar GanatraMarch 7, 2012 at 10:02 AM

    @fbe7db54a197599b3d10d647b7b26a06 if you see the example provided in the post, I'm using cfthread with action ="sleep". 

    ReplyDelete

Post a Comment

Popular posts from this blog

De-obfuscating javascript code in Chrome Developer Tools

I had blogged about JavaScript debugging with Chrome Developer Tools  some time back, wherein I have explained how these developer tools can help in debugging javascript code. Today Google Chrome 12 was released and my Chrome browser was updated to this version. As with every release, there have been some improvements made on performance, usability etc,. One feature that stood out for me is the ability to De-obfuscate the javascript code. What is Minification? Minification is the process of removing unnecessary characters such as white spaces, comments, new lines from the source code. These otherwise would be added to make the code more readable. Minifying the source code helps in reducing the file size and thereby reducing the time taken to download the file. This is the reason why most of the popular javascript libraries such as jQuery are minified. A minified jQuery file is of 31 KB in size where as an uncompressed one is about 229 KB. Unfortunately, debugging minified javascript f
7 comments
Read more

Adding beforeRender and afterRender functions to a Backbone View

I was working on a Backbone application that updated the DOM when a response was received from the server. In a Backbone View, the initialize method would perform some operations and then call the render method to update the view. This worked fine, however there was scenario where in I wanted to perform some tasks before and after rendering the view. This can be considered as firing an event before and after the function had completed its execution. I found a very simple way to do this with Underscore's wrap method.
Post a Comment
Read more

On GraphQL and building an application using React Apollo

When I visualize building an application, I would think of using React and Redux on the front-end which talks to a set of RESTful services built with Node and Hapi (or Express). However, over a period of time, I've realized that this approach does not scale well when you add new features to the front-end. For example, consider a page that displays user information along with courses that a user has enrolled in. At a later point, you decide to add a section that displays popular book titles that one can view and purchase. If every entity is considered as a microservice then to get data from three different microservices would require three http  requests to be sent by the front-end app. The performance of the app would degrade with the increase in the number of http requests. I read about GraphQL and knew that it is an ideal way of building an app and I need not look forward to anything else. The GraphQL layer can be viewed as a facade which sits on top of your RESTful services o
Post a Comment
Read more