client Vs Session

[theDude28]

Hi sorry for another newbie question but I was just wondering when making
variables last the whole time a user is logged in are you best using client or
session variables i am currently using session variables but would there be any
advantages or not if i were to change it to client variables?

Thanks in advance.

[michaelmuller]

If you needed to store structure variables in the user's state container
(client vs session) you would need to use session variables, as client
variables can't store structures. Also, client variables can be set to forever,
whereas session variables eventually time out.

I'm about to pose a similar question regarding using session variables AND
cookies in a new topic. Look for it if you're interested.

[gclausen]

If you only want your variables to last for the duration of the session then
use Session variables. If you want your variables to be available the next time
the same user comes back to your applicatiion then you want to use Client
variables.

Session variables are a little faster since they are stored in CF memory on
the server. Since Client variables are persisted (saved for a long period of
time) they are normally stored in a database.

michaelmuller is right, if you need to store complex datatypes (like
structures or queries) you would need to use Session variables. Client
variables can only be numeric or strings.

[theDude28]

Hi thanks for your reply is it still ok to store session variables in a database for later analysis or would i have to use client variables?

Thanks.

[Unregistered]

Complex objects can be stored in the client, they just need to be serialized first cfwddx can help with this. Obviously doing this for everything would be a pain in the a--