Session vars use shared memory, so when you use them, the server is doing a
bit more work. To keep things safe, simply wrap your session calls (both
reads and writes) with CFLOCK.
The "rule" is: If you type session, server, or application, you should
ALWAYS wrap the code with CFLOCK.
=======================================================================
Raymond Camden, Cold Fusion Jedi Master for Syntegra (www.syntegra.com)
Allaire Certified Instructor and Member of Team Allaire
Email : [EMAIL PROTECTED]
ICQ UIN : 3679482
"My ally is the Force, and a powerful ally it is." - Yoda
> -----Original Message-----
> From: Alan Ford [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 13, 2000 3:44 AM
> To: [EMAIL PROTECTED]
> Subject: Session variables
>
>
> When we need to, we are storing information in Session variables.
> To be nice
> and tidy, when the user logs out (if they do), I delete all of
> 'our' session
> variables from the structure. All works perfectly.
>
> However, I seem to remember reading somewhere that Session
> variables should
> be used sparingly, but I can't remember why. Is there some restriction on
> the use of Session variables?
>
> Thanks in advance,
>
> Alan Ford
>
> ------------------------------------------------------------------
> ------------
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/sp
> ectra_talk or send a message to
> [EMAIL PROTECTED] with 'unsubscribe' in the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
