MACROMEDIA COLFUSION MX 7 - INSTALLING AND USING COLDFUSION MX, Reference

Page: 40 / 1108

40 Chapter 2: ColdFusion Tags
cfapplication
Description
Defines the scope of a ColdFusion application; enables and disables storage of Client variables;
specifies the Client variable storage mechanism; enables Session variables; and sets Application
variable timeouts.
Category
Application framework tags
Syntax
<cfapplication
name = "application_name"
loginStorage = "cookie" or "session"
clientManagement = "yes" or "no"
clientStorage = "datasource_name" or "Registry" or "Cookie"
setClientCookies = "yes" or "no"
sessionManagement = "yes" or "no"
sessionTimeout = #CreateTimeSpan(days, hours, minutes, seconds)#
applicationTimeout = #CreateTimeSpan(days, hours, minutes, seconds)#
setDomainCookies = "yes" or "no"
scriptProtect = "none", "all", or list>
See also
cfassociate
,
cferror
,
cflock
,
cfmodule
; Chapter 5, “Application.CFC Reference,” on
page 945 ; Chapter 13, “Designing and Optimizing a ColdFusion Application” and Chapter 37,
“Integrating J2EE and Java Elements in CFML Applications,” in ColdFusion MX Developer’s
Guide
History
ColdFusion MX 7: Added
scriptProtect
attribute
ColdFusion MX 6.1: Added
loginStorage
attribute
ColdFusion MX:
•
Changed how persistent scopes are available: Server, Session, and Application scope variables
are stored in memory as structures. In earlier releases, only Session and Application scope
variables were stored this way. You cannot access the UDF function scope as a structure.
•
Changed the algorithm for setting the CFTOKEN variable value: if the registry key
UUIDToken is a non-zero value, ColdFusion uses a number constructed from the UUID plus
a random number. Otherwise, ColdFusion sets the CFTOKEN variable default value using a
positive random integer. (In earlier releases, ColdFusion always used a number constructed
from the UUID plus a random number.)