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

How to use the APP_INITIALIZER token to hook into the Angular bootstrap process

I've been building applications using Angular as a framework of choice for more than a year and this post is not about another React vs Angular or the quirks of each framework. Honestly, I like Angular and every day I discover something new which makes development easier and makes me look like a guy who built something very complex in a matter of hours which would've taken a long time to put the correct architecture in place if I had chosen a different framework. The first thing that I learned in Angular is the use of the APP_INITIALIZER token.
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

Using MobX to manage application state in a React application

I have been writing applications using React and Redux for quite some time now and thought of trying other state management solutions out there. It's not that I have faced any issues with Redux; however, I wanted to explore other approaches to state management. I recently came across MobX  and thought of giving it a try. The library uses the premise of  `Observables` to tie the application state with the view layer (React). It's also an implementation of the Flux pattern wherein it uses multiple stores to save the application state; each store referring to a particular entity. Redux, on the other hand, uses a single store with top-level state variables referring to various entities.
Post a Comment
Read more