Adobe Dreamweaver CC 2014 v.13 - Manual (Page 636)

To the top
To the top
ASP and ColdFusion application variables
In ASP and ColdFusion, you can use application variables to store and display information that is maintained for the lifetime of the application and
persists from user to user. The application’s lifetime lasts from the time the first user requests a page in the application to the time the web server
is stopped. (An application is defined as all the files in a virtual directory and its subdirectories.)
Because application variables last for the lifetime of the application, and persist from user to user, they’re ideal for storing information that must
exist for all users, such as the current time and date. The value of the application variable is defined in the application’s code.
ASP server variables
You can define the following ASP server variables as sources of dynamic content: Request.Cookie, Request.QueryString, Request.Form,
Request.ServerVariables, and Request.ClientCertificates.
ColdFusion server variables
You can define the following ColdFusion server variables:
Client variables Associate data with a specific client. Client variables maintain the application’s state as the user moves from page to page in the
application, as well as from session to session. “Maintaining state” means to preserve information from one page (or session) to the next so that
the application remembers the user, and the user’s previous choices and preferences.
Cookie variables Access cookies passed to the server by the browser.
CGI variables Provide information about the server running ColdFusion, the browser requesting a page, and other information about the
processing environment.
Server variables Can be accessed by all clients and applications on the server. They persist until the server is stopped.
Local variables Created with the CFSET tag or CFPARAM tag within a ColdFusion page.
More Help topics
Legal Notices | Online Privacy Policy
629