On 7/16/01, Mike Kear penned:
>I hope you guys can help me, because I'm a newbie to multi-server clustered
>environment and I'm getting more confused every day as I try to wrestle with
>client variables, only to find every turn I take leads me to a dead end
>street.
>
>I have no access to the administrator, the registry or anything at all
>central. In fact it takes a week or more to get a response from the system
>administrator (which is another story that's giving me food for thought
>about where I host my sites!) I have to implement an authentication system
>on a site where I have to use client variables, because it's a cluster
>environment, and I am not allowed to rely on any central variable storage.
Is this site on the same system where you're talking about not having
access? I'd imaging if it's a clustered environment they'd already
have a default SQL database for client storage.
>So that means I have to use cookies, and a table in my SQLServer7 datasource
>to keep track of all the CFIDs and CFTOKENS. (Is that correct? If not I'm
>barking up the wrong tree entirely!)
>
>Therefore, I have to create a table in my datasource to keep hold of all the
>sessions. What fields should I have in my table if all I want to do is just
>identify one user session from another? If I want to hold the levels of
>access data too, should I keep that in there or go back to the users table
>every page looking for that info?
As Dave said, the required fields are created automatically. I think
he left out though that the datasource has to be specified as a
client variables repository in CF administrator.
The big thing about storing client variables is if you want to store
any complex structures, you'll have to serialize them into wddx then
convert them back to cfml when you need them.
>And how do I maintain this table so it doesn't just get bigger and bigger
>forever?
With SQL Server, this can be done automatically depending on the
backup method. The data part of the database will stay manageable
since the data is purged at the intervals specified in CF
administrator. The transaction log will grow forever though unless
the database is backed up. Then when the transaction logs are backed
up, you can specify to Shrink Database Automatically in which case
all transactions before the point of the last full backup are purged.
At least I THINK that's how it works.
--
Bud Schneehagen - Tropical Web Creations
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
ColdFusion Solutions / eCommerce Development
[EMAIL PROTECTED]
http://www.twcreations.com/
954.721.3452
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
