Installation guide

New CFID/CFTOKEN values are assigned only when a client/browser executes a CFML
page for the first time without those cookies already set.
3.7 Client Variable Processing
There are some differences between BlueDragon and ColdFusion in the underlying
implementation of client variable processing with regard to using a database to store the
client variables.
First, where ColdFusion requires an administrator to configure a datasource to serve as a
client variable repository, BlueDragon does not. If a datasource is specified in the
CFAPPLICATION ClientStorage attribute (or indeed in the administration console when
setting a default client storage datasource, if desired), BlueDragon will store client vari-
ables there without need to prepare the datasource to hold client variables.
Note as well that BlueDragon will not create the table needed within the datasource
(
BDCLIENTDATA) until a page is processed that references client variables.
BlueDragon does not currently support an option to expire client variables due to inactiv-
ity. This is planned for a future update.
Additionally, in ColdFusion, when client variables are stored in a datasource they are
stored in a table named
CDATA that uses two columns as the primary key: CFID (which is a
combination of CFID:CFTOKEN) and APP (which is the application name as specified in
CFAPPLICATION). Therefore, client variables are stored per-application so that they are
only retrieved and visible within the named application.
BlueDragon currently stores all client data in a single table named
BDCLIENTDATA, which
has a primary key of only
CFID (the CFID:CFTOKEN combination). This means that client
variables are not stored per-application (client variables created for a user in one applica-
tion are visible to that user in another application—but each client’s variables are unique
to them as individual visitors).
BlueDragon 6.1 CFML Compatibility and Reference Guide 6