Kristin
Wow! Thanks for replying to this question in such detail. I didn't know so many famous
CF authors were on this
list! :-)
I know the default timeout for client vars is usually set to be 10 days or something
long but as I understand it
they do exactly the same as session varialbes in maintain info across page requests
for one user. For me the "no
locking required" benefit outweights the having to set up a database to store them in
(which the CF Admin does for
you when you create a client var datasource).
To deal with the long time out I usually store the date/time of the last page access
in a client var and if the
difference between it and current time gets greater than the timeout I want then I
CFLOCATION the page to the login
screen.
- Michael Smith, TeraTech, Inc http://www.teratech.com/
Kristin Aileen Motlagh wrote:
> [snip]
> Also, to Michael Smith's comment:
>
> "If you don't have any structures or queries in the
> session vars it would be
> best to convert to client vars (stored
> in database rather than registry) as these don't need
> locks at all..."
>
> Sessions and client management have two different
> purposes. Session management is meant for a short
> period of time, and does not need data source setup.
> Client variables are meant to persist over multiple
> sessions. It is funny because when session variables
> first came out...everyone was saying...stop using
> client variables!! But I think you need to judge based
> upon your purpose and application what is best. Do you
> use them interchangeably?
>
> -Kristin
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
