So as far as variables go (putting aside CFFILE considerations, and some
others mentioned by Forta such as CFX tags that aren't multithread safe and
CFHTTP) -- AND IF I have only:
APPLICATION scoped variables that once set are read only
VARIABLES scoped variables, and
CLIENT scoped variables
and no other non-scoped variables,
then I don't have to worry about CF locking.
Right? Wrong?
best, paul
At 02:48 PM 8/19/00 -0400, you wrote:
>On 8/19/00, paul smith penned:
> >Does the following mean you let the database take care of locking
> >client variables and you don't bother CF with this little detail?
>
>Client variables are written to a database or the registry and
>therefore are not susceptible to problems caused by multiple users
>writing variables to memory, or reading while others are writing
>variables to memory and so do not need to be locked.
>
>That's the one thing I've learned. LOL
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
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.
