Table of Contents
Advertisement
222
About client cookies
Both types of variables normally require ColdFusion to store two client identification
variables as cookies on the client's system:
These cookies uniquely identify the client to the ColdFusion Server, which also
maintains copies of the variables. You can configure your application so that it does
not use client cookies at all, but you must then pass these variables to all pages your
application calls.
Managing client state in a clustered environment
To maintain your application's client state in a clustered server environment, you
can store the server-side client identification variables in a common, back-end
repository that all Web servers in a multiserver clustered environment can access.
You enable use of a common repository by specifying the
setdomaincookies
This attribute specifies that the server-side copies of the CFID and CFToken
variables used to identify the client to ColdFusion are stored at the domain level (for
example, .macromedia.com). If CFID and CFToken combinations already exist on
each host in the cluster, ColdFusion migrates the host-level variables on each cluster
member to the single, common domain-level variable. Following the setting or
migration of host-level cookie variables to domain-level variables, ColdFusion
creates a new cookie variable (CFMagic) that tells ColdFusion that domain-level
cookies have been set.
Managing client state without cookies
You can use ColdFusion's client state management without cookies, however, this is
not recommended. If you choose to maintain client state without cookies, you must
ensure that every request carries the CFID and CFToken variables.
To maintain client state without cookies, set the
cfapplication
CFToken between pages, either in hidden form fields or appended to URLs. You
accomplish this using the variable
values of these two variables are the same.)
CFID, a sequential client ID
CFToken, a random-number client security token
attribute in your Application.cfm page.
tag to No. Then, you must maintain client state by passing CFID and
Chapter 12 Using the Application Framework
setClientCookies
or
Client.URLToken
cfapplication
attribute of the
. (The
Session.URLToken
Advertisement
Table of Contents
