From DAT New Wiki
Jump to: navigation, search

Research notes for WEF project:

ColdFusion history

  • 1995 - ColdFusion 1.0
  • 1998 - ColdFusion 3.1
  • 1999 - ColdFusion 4.0

In 2001, Allaire (creator of ColdFusion) merged with Macromedia

  • Session variables are always stored in memory
  • client variables can be stored in a database
  • both rely on cookies unless you explicitly pass Session.URLTOKEN between pages (either in hidden form fields or appended to URLs)
  • The ColdFusion client structure is a list of variables which you create and access with a "client" prefix
  • You enable client management in the CFAPPLICATION tag, at the beginning of Application.cfm and there you specify whether client variables should be stored in the system registry, a data source or cookies
  • When client state management is enabled for an application, you can create a client variable by simply prefixing it with "Client", e.g.:
 <CFSET Client.FavoriteColor="Red">
  • Once a client variable has been set in this manner, it is available for use within any application page in your application that is accessed by the client for whom the variable is set
  • In addition to storing custom client variables, the Client object has several standard parameters which include the I.D. used to track the individual client, the time the I.D. was created, hit count, and when the client’s last visit was
  • without cookies, you can’t recognize a returning client, and you’ll have to pass the client or session ID between forms explicitly through the url or hidden form fields (broken link)

  • You can prevent ColdFusion from sending client information to the browser as cookies by setting the setClientCookies attribute of the cfapplication tag to No.
  • ...