Adobe 38000827 Administration Guide - Page 19

externally use two small database tables, like those shown in the following tables

Page 19 highlights

The following table compares these storage options: Storage type Advantages Data source • Can use existing data source • Portable: not tied to the host system or operating system Browser cookies • Simple implementation • Good performance • Can be set to expire automatically • Client-side control System registry • Simple implementation • Good performance • Registry can be exported easily to other systems • Server-side control Disadvantages • Requires database transaction to read/write variables • More complex to implement • Users can configure browsers to disallow cookies • ColdFusion MX limits a cookie's data to 4 KB • Netscape Navigator allows only 20 cookies from one host; ColdFusion MX uses three cookies to store read-only data, leaving only 17 cookies available • Possible restriction of the registry's maximum size limit on Windows in the Control Panel • Integrated with the host system: not practical for clustered servers • Solaris, Linux, and HP-UX registries are text files. Their registries deliver slow performance and low scalability. Migrating client variable data To migrate your client variable data to another data source, you should know the structure of the database tables that store this information. Client variables stored externally use two small database tables, like those shown in the following tables: CDATA Table Column cfid app data Data type CHAR(64), TEXT, VARCHAR, or equivalent CHAR(64), TEXT, VARCHAR, or equivalent MEMO, LONGTEXT, LONG VARCHAR, or equivalent CGLOBAL Table Column Data type cfid CHAR(64), TEXT, VARCHAR, or equivalent data MEMO, LONGTEXT, LONG VARCHAR, or equivalent lvisit TIMESTAMP, DATETIME, DATE, or equivalent Server Settings section 11

  • 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

Server Settings section
11
The following table compares these storage options:
Migrating client variable data
To migrate your client variable data to another data source, you should know the
structure of the database tables that store this information. Client variables stored
externally use two small database tables, like those shown in the following tables:
Storage type
Advantages
Disadvantages
Data source
Can use existing data
source
Portable: not tied to the
host system or operating
system
Requires database transaction to
read/write variables
More complex to implement
Browser cookies
Simple implementation
Good performance
Can be set to expire
automatically
Client-side control
Users can configure browsers to
disallow cookies
ColdFusion MX limits a cookie’s
data to 4 KB
Netscape Navigator allows only 20
cookies from one host; ColdFusion
MX uses three cookies to store
read-only data, leaving only 17
cookies available
System registry
Simple implementation
Good performance
Registry can be exported
easily to other systems
Server-side control
Possible restriction of the registry’s
maximum size limit on Windows in
the Control Panel
Integrated with the host system: not
practical for clustered servers
Solaris, Linux, and HP-UX registries
are text files. Their registries deliver
slow performance and low
scalability.
CDATA Table
Column
Data type
cfid
CHAR(64), TEXT, VARCHAR, or equivalent
app
CHAR(64), TEXT, VARCHAR, or equivalent
data
MEMO, LONGTEXT, LONG VARCHAR, or equivalent
CGLOBAL Table
Column
Data type
cfid
CHAR(64), TEXT, VARCHAR, or equivalent
data
MEMO, LONGTEXT, LONG VARCHAR, or equivalent
lvisit
TIMESTAMP, DATETIME, DATE, or equivalent