User Guide

Table Of Contents
342 Chapter 15: Using Persistent Data and Locking
Using variables in clustered systems
Because memory variables are stored in memory, they are not available to all servers in a cluster.
As a result, you generally do not use Session, Application, or Server scope variables in clustered
environment. However, you might use these scope variables in a clustered system in the following
circumstances:
If the clustering system supports “sticky” sessions, in which the clustering system ensures that
each user session remains on a single server. In this case, you can use session variables as you
would on a single server.
You can use Application and Server scope variables in a cluster for write-once variables that are
consistently set, for example, from a database.
To use client variables on a clustered system, store the variables as cookies or in a database that is
available to all servers. If you use database storage, on one server only, select the Purge Data for
Clients that Remain Unvisited option on the Client Variables, Add/Edit Client Store page in the
Server Settings area in the ColdFusion MX Administrator.
For more information on using client and session variables in clustered systems, see “Managing
client identity information in a clustered environment” on page 346.
Managing the client state
Because the web is a stateless system, each connection that a browser makes to a web server is
unique to the web server. However, many applications must keep track of users as they move
through the pages within the application. This is the definition of client state management.
ColdFusion provides tools to maintain the client state by seamlessly tracking variables associated
with a browser as the user moves from page to page within the application. You can use these
variables in place of other methods for tracking client state, such as URL parameters, hidden form
fields, and HTTP cookies.