Client variables areaeated
for each client that visits. H data for old clients that have not recently visited is not deleted, eventually the size of client variable storage will grow large ..By enabling this option and specifying a reasonable delay before purging client variables (this generally depend dent on the nature of your applications), you can keep the size of the client variable store small and efficient.
Disable Global Client Variable Updates
This setting relates to global variables such as Hit-count and Last Visit. H you allow updates to be disabled, these variables are updated by ColdFusion NLRB when they are modified or set; otherwise, they are updated for each page request.
Create Client Data abase Tables
The first time you add data for client storage, Cold-Fusion will need to create tables for storing the client data. Therefore, only enable this option the first time you add a data source to the client storage list You can add any number of data sources to the list and then select individual data sources for particular applications by using the Counterintelligence of the CFAPPLlCATION tag in your Application.
Next, the Client Variable Storage screen allows the selection of a default location for storage of client variables when no alternate location is specified with the CFAPPLICATION tag. The possible options for the default location are Cookie for client browser cookies, Registry for the system registry, or any data you added. Finally, the Client Variable Storage screen allows the selective enabling or disabling of application and session variables and allows the specification of maximum and default timeouts for both types of variables, The default will be used if no timeout is specified in the CF Application tag (or an application. If a value is specified but it exceeds the maximum timeout, then the maximum timeout will be used.
The Java Settings screen also used to specify [ava-related settings so that Cold Fusion can ‘work with Java on the server:
Load JVM when starting
Cold Fusion If this setting is enabled, ColdFusion will load the Java Virtual Machine when it starts. Otherwise, it will wait until the first request that requires the Virtual Machine before loading it.
Java Virtual Machine
Path This field is used to specify the complete path and filename of the Java Virtual Machine on your system.
This field is used to specify the class path for your system. Cold Fusion uses this.path to locate Java classes and Enterprises specified using the CF-OBJECT tag or the CreateQbj ect function. The path can be a series of directories separated by semi-colons or a single directory.
Heap Size This field is used to specify the Java Virtual Machine’s initial heap size in kilobytes. If you are unsure of what is appropriate for your system, use the default of 1024 kilobytes. Maximum Heap Size This field is used to specify the maximum heap size for the Java Virtual Machine in kilobytes. If you are unsure what is appropriate for your system, use the default of 16384 kilobytes.
Options Use this field to specify initialize I options for the Java Vt-actual Machine in the form <name>=<value>; <name=value ‘) <name>=<value> CFX Jar Path This field specifies the directory containing the ColdFusion cfx , jar file which contains the interfaces necessary to enable Java-based
in ColdFusion 4.5. If ColdFusion is installed in c: \fusion on, this directory will normally be c: \fusion on java lasses.
The Variable Locking screen is used to specify how Cold Fusion Server 4.5 and above should handle variable locking. Four settings are available on the screen:
Single Threaded Sessions
When enabled, requests will be threaded by session ID to ensure that no potential variable locking conflicts can occur by simultaneous requests from the same session.
‘This setting is used to specify how server scope variables should be locked. The possible choices are: No automatic checking or locking (the developer has to ensure that variables are properly locked with the CFLOCK tag), Full checking (Cold- Fusion checks all variables to make sure they are properly locked), Automatic read locking (ColdFusion checks all server variables to make sure they are properly locked when writing and automatically locks variables for reads).
This setting is used to specify how application scope variables should be locked. The possible choices are: No automatic checking or locking (the developer has ensure that variables are properly locked with the CFLOCK tag), Full checking (ColdFusion checks all variables to make sure they are properly locked), Automatic read l&king (ColdFusion checks all server variables to make sure they are properly locked when writing and automatically locks variables or reads).