Adobe 38000827 Administration Guide - Page 18

Client Variables Developing ColdFusion MX Applications, with CFML

Page 18 highlights

Setting Description Trusted cache Enable this option if you want ColdFusion MX to use cached templates without checking whether they changed. For sites that are not updated frequently, using this option minimizes file system overhead. Limit the maximum number of cached queries on the server to [n] queries Enable this option by entering a value to limit the maximum number of cached queries that the server maintains. Cached queries allow retrieval of result sets from memory rather than through a database transaction. Because queries reside in memory, and query result set sizes differ, you must provide a limit for the number of cached queries. You enable cached queries with the cachedwithin or cachedafter attributes of the cfquery tag. Client Variables page Client variables let you store user information and preferences between sessions. Using information from client variables, you can customize page content for individual users. You enable client variable default settings in ColdFusion MX on the Client Variables page of the Administrator. ColdFusion MX lets you store client variables in the following ways: • In a data source If your data source uses a bundled JDBC driver, ColdFusion can automatically create the necessary tables. If your data source uses the ODBC Socket or a third-party JDBC driver, you must manually create the necessary CDATA and CGLOBAL database tables. For more information, see Developing ColdFusion MX Applications with CFML. • As cookies in users' web browsers • In the operating system registry Caution: Macromedia recommends that you do not store client variables in the registry because it can critically degrade performance of the server. If you do use the registry to store client variables, you must allocate sufficient memory and disk space. You can override settings specified in the Client Variables page using the attributes of the cfapplication tag. For more information, see Developing ColdFusion MX Applications with CFML. 10 Chapter 2 Basic ColdFusion MX Administration

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68

10
Chapter 2
Basic ColdFusion MX Administration
Client Variables page
Client variables let you store user information and preferences between sessions. Using
information from client variables, you can customize page content for individual users.
You enable client variable default settings in ColdFusion MX on the Client Variables
page of the Administrator. ColdFusion MX lets you store client variables in the following
ways:
In a data source
If your data source uses a bundled JDBC driver, ColdFusion can automatically create
the necessary tables. If your data source uses the ODBC Socket or a third-party
JDBC driver, you must manually create the necessary CDATA and CGLOBAL
database tables. For more information, see
Developing ColdFusion MX Applications
with CFML
.
As cookies in users’ web browsers
In the operating system registry
Caution:
Macromedia recommends that you do not store client variables in the registry
because it can critically degrade performance of the server. If you do use the registry to
store client variables, you must allocate sufficient memory and disk space.
You can override settings specified in the Client Variables page using the attributes of the
cfapplication
tag. For more information, see
Developing ColdFusion MX Applications
with CFML
.
Trusted cache
Enable this option if you want ColdFusion MX to use cached
templates without checking whether they changed. For sites that
are not updated frequently, using this option minimizes file system
overhead.
Limit the maximum
number of cached
queries on the server
to [n] queries
Enable this option by entering a value to limit the maximum number
of cached queries that the server maintains. Cached queries allow
retrieval of result sets from memory rather than through a database
transaction. Because queries reside in memory, and query result set
sizes differ, you must provide a limit for the number of cached
queries. You enable cached queries with the
cachedwithin
or
cachedafter
attributes of the
cfquery
tag.
Setting
Description