Danesh's book very very good on client-session management page 435: Using Built-in
session variables held in RAM. Session.CFID, Session.CFTOKEN, Session.URLTOKEN,
Session.SessionID.
The reason for not using session variable scope in a sever cluster atmosphere. If they
are held in RAM on one server and load-balancing changes servers what is in Ram stays
in the
original server's RAM.
paul smith wrote:
> Developing Web Applications with ColdFusion 4 has the following on p 76:
>
> "Because session variables no longer require client variables to be turned
> on, the following read-only variables have been added to the session
> variable scope: CFID, CFTOKEN, and URLTOKEN."
>
> best, paul
>
> At 09:37 AM 5/19/00 -0700, you wrote:
> >CF Server takes care of deleting, etc., the session variables. They are
> >entirely based upon CFID and CFToken. Remember that CFID and CFToken are
> >client scope, not session scope.
>
> ------------------------------------------------------------------------------
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
>message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
