Just to add more to why I believe a client scope is better than a
session scope, and can be backed up in an article written in the
Coldfusion Developers Journal.
When using session variables in a clustered environment, you will need
to have software or hardware to maintain sticky sessions. Now as the
article explains and I have seen this for myself, if a user is stuck to
a server and that server falls over for any reason this user will loose
their session state. Because they will be shifted to the next server in
the cluster, which means they will loose the session scope and start to
cause problems.
If this has not happened to you yet then consider yourself lucky, but
the truth is that it can and will happen at some point in your life as a
developer.
I do recommend reading this article, it is well worth the read and backs
up my statement better.
Look bottom line is each developer as their own methods, practices etc.
And if it works for you then by all means keep going with it, however
problems can arise if the server a user was connected to ever falls over
for any reason.
Keeping this in mind I use client variables, now as I also have a
different method of programming in CF than most people I am able to have
full control of my application, thus ensuring not only full security but
making a user feel the servers are always up and running using the above
advice.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
