For the session timeout, I went with one second. If detected, we are acting on it in two ways: we kill the session timeout within the pseudo constructor and, we clear the user session cookies within the onRequestStart() event handler.

In this Application.cfc ColdFusion framework component, notice that we are looking for the URL flag, killSession. In this approach, we're going to listen for a URL flag from within the Application.cfc pseudo constructor and, if detected, we're going to kill the user's session timeout for the given request. This gives us the ability to, on every single page request, dynamically change the current settings for both the application as well as for the session associated with the given request.

Approach One: Changing The Session Timeout In The Application.cfc Pseudo ConstructorĪs has been demonstrated before, the Application.cfc ColdFusion framework component is instantiated for every single page request in a given application. All of these solutions revolve around dynamically changing a given user's session timeout but each differs in terms of its organization and use of documented vs. As a follow-up post, I thought it would be good to explore a few different approaches to ColdFusion session termination.

Not only did I learn a thing or two, it got me thinking about the ways in which we can actually end a user's ColdFusion session. Yesterday's post on the misconceptions behind clearing the ColdFusion Session scope sparked some really great conversation in the comments.

Coldfusion user define session variable