I discuss the topic of using client variables to manage a codebase in a
clustered environment, in my CFDJ article from last year. You can find it
online at
http://www.advantex.net/index.cfm/fuseaction/showCFDJArticle.cfm
This article also provides some insight as to why you might NOT want to
stick a session on just ONE server in a clustered environment.
Hope this helps,
.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Marc Funaro, President
Advantex Technical Consulting Services
5547 State Highway 12
Norwich, NY 13815
Phone: 607-336-6895
Fax: 801-383-4864
Internet: http://www.advantex.net
Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-----Original Message-----
From: Mark Stewart [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 02, 2001 8:51 AM
To: CF-Community
Subject: Re: Client versus Session...
IMO, I don't think one is better than the other. I honestly don't think that
you can make a blanket statement that says, "client variables are better
than session variables" or visa versa. I've always believed in letting the
situation dictate what type of variable structure I'm going to use. In a lot
of cases, I've used a happy mix of all of them. Both client and session
variables have their good and bad points. For instance, a company intranet
would be fine with session variables and a high traffic, clustered site
might be better off with client variables. Now, I don't buy into the fact
that if you're clustering a site, you shouldn't use session variables. What
if you set up the cluster where when a session starts, that session stays on
one box and one box only. When that box reaches it's threshold, all new
sessions go to the next box in the cluster. In this situation, you don't
have to worry about tracking sessions over multiple boxes and you could
therefore summarize that session variables would be fine. Of course, as long
as there is enough memory. But then again, during your discovery phase, you
should have a good idea what kind of traffic you're expecting, how many
session variables (approximately) you'll be using and calculate the session
variables memory cost and then build your box accordingly. I know that
sounds great in theory and probably a lot of people don't do that but it's a
good practice.
Just my .02
Mark - with a K :-)
Mark Stewart
Programmer/Analyst
Communication Concepts
215.672.6900 x1332
>>> [EMAIL PROTECTED] 05/02/01 01:06AM >>>
Since there seems to be a few people still up and about, could you put your
thinking cap on for a sec.......
Session versus Client. I've read through just about every post I could find
on the subject throughout CF-Talk. And the consensus is that client is the
way to go.
So....
I am about to convert a site that I have been having long-standing issues
with timing out, etc. Is it really as simple as turning all the
session.whatevers into client.whatevers and making sure clientmanagement is
turned on? (this is a hosted app and by default, they store client vars in a
SQL database).
Thanks for thinking so late....I'm going to bed soon I promise.....
Erika
(with a *K*)
"Whatever you can do, or dream you can, begin it. Boldness has genius,
power, and magic in it." - Goethe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
