ColdFusion Client vs Session Variables

I have a pretty big application that works great and makes extensive use of session variables

We want to insert it into the cloud and run several instances. Unfortunately, our cloud partner does not offer SSL stick sessions, and even if they did, I’m not sure if this is the way to go.

What I would rather do is not rely on the user maintaining the session on the server, and I can achieve this with client variables.

I am interested, however, are there any flaws, are some types of variables that are not working with client variables structs / query, etc. too slow?

There are over 1,500 lines of code using session variables, and I could just search and replace, or I need to go through hundreds of components and rethink them.

+7
source share
2 answers

Yes, client variables are limited in what they can store.

From documents : client variables should be simple data types: strings, numbers, lists, booleans, or date and time values. They cannot be arrays, recordsets, XML objects, query objects, or other objects.

+5
source

Client variables are limited to simple variables such as strings, numbers, etc. But I use a client variable to store the structure and array by serializing in JSON. On many sites, I used a client variable to remember the values ​​of the form fields (especially search criteria), so when the user returns, we can get their last status.

What I need to do while maintaining its serialization and returning to deserialization.

Hope for this help

+3
source

All Articles