MACROMEDIA COLDFUSION 4.5-CFML LANGUAGE, Reference

Page: 37 / 608

Chapter 1: ColdFusion Tags 13
CFAPPLICATION
Defines scoping for a ColdFusion application, enables or disables storing client
variables, and specifies a client variable storage mechanism. By default, client
variables are disabled. Also, used to enable session variables and to set timeouts for
both session and application variables. Session and application variables are stored in
memory.
Syntax
<CFAPPLICATION NAME="Name"
CLIENTMANAGEMENT="Yes/No"
CLIENTSTORAGE="Storage Type"
SETCLIENTCOOKIES="Yes/No"
SESSIONMANAGEMENT="Yes/No"
SESSIONTIMEOUT=#CreateTimeSpan(days, hours,
minutes, seconds)#
APPLICATIONTIMEOUT=#CreateTimeSpan(days, hours,
minutes, seconds)#
SETDOMAINCOOKIES="Yes/No"
>
NAME
The name you want to give your application. This name can be up to 64 characters
long. Required for application and session variables to work. Optional for client
variables.
CLIENTMANAGEMENT
Optional. Yes or No. Enables client variables. Default is No.
CLIENTSTORAGE
Optional. Specifies the mechanism for storing client variables:
•
datasourcename — ColdFusion stores client variables in the specified ODBC or
native data source. To use this option you must create a client variable storage
repository using the Variables page of the ColdFusion Administrator.
•
Registry — ColdFusion stores client variables in the system registry. This is the
default.
•
Cookie — ColdFusion stores client variables on the client machine in a cookie.
Storing client data in a cookie is scalable to large numbers of clients, but this
storage mechanism has some limitations. Chief among them is that if the client
turns off cookies in the browser, client variables won’t work.
SETCLIENTCOOKIES
Optional. Yes or No. Yes enables client cookies. Default is Yes.
If you set this attribute to "NO", ColdFusion does not automatically send the CFID
and CFTOKEN cookies to the client browser; you must manually code CFID and
CFTOKEN on the URL for every page that uses Session or Client variables.