Dave,
Please help! <smile> This whole concept of <cflock> for application
and session variables has me totally stumped. I am using CF 4.01
application server and can't seem to get my mind around the <cflock>
concept.
As I understand it (from CF WACK 4.0) application variables are used
when an application need only set it once then read it often. Such as
Setting the DSN name (application.dsn="somedatabase") or a base
reference application.basref=http://mydomain.com/ in the
applicationcfm file, and session variables are user specific storage
like setting and reading the user ID <session.UserID="1235"> for that
session.
Application variables are available to every session but session
variables are available only to their session.
OK, Now my question is: If I only set the application variable once on
startup and only read it throughout the application why is it
necessary to <cflock> every read of the variable? Doesn't this defeat
the purpose of setting it once for all sessions then reading it often?
If you have to cflock each read, what is the value of the application
scope? Why not use standard variables set in the Application.cfm file
since you don't need to cflock them?
I am absolutely sure I am totally misunderstanding something. Can you
help this poor soul?
Best Regards,
Dennis Powers
UXB Internet
(203)879-2844
http://www.uxbinfo.com
-----Original Message-----
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 04, 2000 3:01 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Yet another CFLOCK question.......
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
