One option is to use client vars, but they cannot store complex vars and changing from session to client scope is a PITA in any sizeable app.
here is one trick I have used. as u know there is a cookie on the users machine which identifies the session, it contains the cfid and cftoken or JessionID if your using that, Whenever a session is created/changed, dump the contents out to WDDX or JSON file on a network shared resource using the info form the cookie as the filename. If the session cookie exists but the data doesn't exist, check for this this file and load it if it does exist. In addition this also provides you with you with session storage in case cf dies, the users do not lose their session data as it will be reloaded when cf restarts. Don't forget to run a schedule to cleanup old files. HTH Russ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:348042 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
