Flash Storage
There are times where you need to store user related variables in some kind of permanent storage then relocate the user into another section of your application, be able to retrieve the data, use it and then clean it. All of these tedious operations are definitely doable but why reinvent the wheel if we can have the platform give us a tool for maintaing conversation variables across requests. The key point for Flash RAM is where will the data be stored so that it is unique per user. ColdFusion gives us several persistent scopes that we can use and we have also created several flash storages for this purpose. Since the ColdBox flash scope is based on an interface, the flash scope storage can be virtually anywhere. You will find all of these implementations in the following package: coldbox.system.web.flash. In order to choose what implementation to use in your application you need to tell the ColdBox.cfc
which one to use via flash configuration structure:
Configuration
Below is a nice chart of all the keys in this configuration structure so you can alter behavior of the Flash RAM objects:
Core Flash Implementations
The included flash implementations for ColdBox are:
Configuration Properties
Each RAM implementation can also use properties in order to alter its behavior upon construction via the properties
configuration struct. Below are the properties our core implementations can use:
Session Flash Settings
none
Cluster Flash Settings
none
Client Flash Settings
none
Mock Flash Settings
none
Cache Flash Settings
cacheName
: The cache provider name declared in CacheBox
Last updated