You're talking about client variables, not session variables. However:
They are as safe as they were in the registry as they are keyed on the
CFID/CFTOKEN pair which are generated by CF. Make sure in your
<CFAPPLICATION...> you have UseDomainCookes set to TRUE so that no matter
which server you happen to being serviced by, the cookies that were set by
one machine will be available to one of the others in the farm.
Performance-wise, your system will thank you for moving to a RDBMS in the
long run as the registry isn't the most efficient of databases and that's
basically what you're using it for by storing client variables in there.
After a while the registry fills up and system performance degrades - a bad
bad thing!
Steve
-----Original Message-----
From: Andres Leon [mailto:[EMAIL PROTECTED]]
Sent: 22 March 2001 16:57
To: CF-Talk
Subject: Session variables stored in SQL server
Hello all,
I am wondering if anyone has had any experience with this:
I am running a IIS5.0 and CF cluster of 5 servers and one databaser
server (sql70) will upgrade to sql2k soon.
I was adviced by Allaire to move my session variables to the database,
rather than storing them in each server's registry.
My question is: How safe is this in terms of client variables getting
mixed, or users taking other each other's session variables becuase they
would be extracted from one pool, rather than 5?
Is there a performance change by moving these variables to a remote
database? good?, bad?
Any thoughts or ideas on the subject will be greatly appreciated.
Thank you!
Andres
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
