Thank you to all of you on CF-Talk for your suggestions ... I'm going to
have a look at them over this weekend, along with a tutorial I found on
client variables, and I hope that all this information is going to give me
what I need.
I hope it's ok to email you again if there's any point of clarification I
need.
But thanks a whole lot for going to the effort to reply to me.
Cheers,
Mike Kear
Windsor, NSW, Australia
AFP WebWorks
-----Original Message-----
From: Brook Davies [mailto:[EMAIL PROTECTED]]
Sent: Sunday, June 17, 2001 6:29 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Surely someone can help me ... Please?
You do not need to use the cfregistry. I recommend using a database to store
your client variables in. Its actually rather easy once you understand the
concepts. CF does alot of the work for you.
To start set up a new database.
1.Name it something like "myproject_clientvars". Do not create any tables in
the db.
2. Create a datasource on the server for this newly created database.
3.Next, go to the cfadministrator and select the "variables" section. Under
the heading Client Variable Storage, select your newly created client
variable repository database from the drop down and click ADD.
Make sure that "create client tables" is checked. This will generate the
tables to support your client variables. The other two settings are less
important. Read the description, they are fairly self explanatory.
Now you have a client variable repository configured. The next step is to
instruct your application(s) to use this particular datasoure to store
client variables in. To do this you specify it within your <cfapplication>
tag. Here is an example:
<cfapplication name="myproject" clientmanagement="yes"
clientstorage="myproject_clientvars">
Now, throughout this application, whenever you set a client variable. It
will be written to the database you configured above. If you went through
your entire application and simply changed all of the session variables to
client variables, your application would essentially work. Cold Fusion will
seemlessly write all of the client variables to the db per page request.
These variables are then available throughout your application.
Now the final part, and probably the most difficult is handling
authentication and session expiration. But then again, it's not really that
complicated. Since you can not as easily "time out", or "expire" client
variables, you need to handle this yourself.
You do this by creating a clientVar after a user successfuly logs into your
application. In my apps, I
[snip]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
