
328
Chapter 15: Using Persistent Data and Locking
Enabling session variables in your application
You must also enable session variables in the
cfapplication
tag in your Application.cfm file. Do
the following in the Application.cfm file to enable session variables:
•
Set
sessionManagement="Yes"
•
Use the
name
attribute to specify the application's name.
•
Optionally, use the
sessionTimeout
attribute to set an application-specific session time-out
value. Use the
CreateTimeSpan
function to specify the number of days, hours, minutes, and
seconds for the time-out.
The following sample code enables session management for the GetLeadApp application and sets
the session variables to time out after a 45-minute period of inactivity:
<cfapplication name="GetLeadApp"
sessionmanagement="Yes"
sessiontimeout=#CreateTimeSpan(0,0,45,0)#>
Storing session data in session variables
Session variables are designed to store session-level data. They are a convenient place to store
information that all pages of your application might need during a user session, such as shopping
cart contents or score counters.
Using session variables, an application can initialize itself with user-specific data the first time a
user accesses one of the application’s pages. This information can remain available while that user
continues to use that application. For example, you can retrieve information about a specific user’s
preferences from a database once, the first time a user accesses any page of an application. This
information remains available throughout that user’s session, thereby avoiding the overhead of
retrieving the preferences repeatedly.
Standard session variables
If you use ColdFusion session variables, the Session scope has four built-in, read-only variables
that your application can use. If you use J2EE session management, the Session scope has two
built-in variables. Generally, you use these variables in your ColdFusion pages only if your
application supports browsers that do not allow cookies. For more information on supporting
browsers that do not allow cookies, see
“Using client and session variables without cookies”
on page 319
. The following table describes the built-in session variables.
Variable
Description
Session.CFID
ColdFusion session management only: the client ID, normally stored on the
client system as a cookie.
Session.CFToken
ColdFusion session management only: the client security token, normally
stored on the client system as a cookie.
Summary of Contents for ColdFusion MX
Page 1: ...Developing ColdFusion MX Applications...
Page 22: ...22 Contents...
Page 38: ......
Page 52: ...52 Chapter 2 Elements of CFML...
Page 162: ......
Page 218: ...218 Chapter 10 Writing and Calling User Defined Functions...
Page 250: ...250 Chapter 11 Building and Using ColdFusion Components...
Page 264: ...264 Chapter 12 Building Custom CFXAPI Tags...
Page 266: ......
Page 314: ...314 Chapter 14 Handling Errors...
Page 344: ...344 Chapter 15 Using Persistent Data and Locking...
Page 349: ...About user security 349...
Page 357: ...Security scenarios 357...
Page 370: ...370 Chapter 16 Securing Applications...
Page 388: ...388 Chapter 17 Developing Globalized Applications...
Page 408: ...408 Chapter 18 Debugging and Troubleshooting Applications...
Page 410: ......
Page 426: ...426 Chapter 19 Introduction to Databases and SQL...
Page 476: ...476 Chapter 22 Using Query of Queries...
Page 534: ...534 Chapter 24 Building a Search Interface...
Page 556: ...556 Chapter 25 Using Verity Search Expressions...
Page 558: ......
Page 582: ...582 Chapter 26 Retrieving and Formatting Data...
Page 668: ......
Page 734: ...734 Chapter 32 Using Web Services...
Page 760: ...760 Chapter 33 Integrating J2EE and Java Elements in CFML Applications...
Page 786: ...786 Chapter 34 Integrating COM and CORBA Objects in CFML Applications...
Page 788: ......