> I understand why it is important to lock session variables but I don't
> understand why it is important to lock application variables, especially
when
> they are the same for everyone. Basically, I only use application
variables to
> name my db information (db source, username, password, etc).
Locking is necessary for ALL shared scopes: session, application, server.
The reason is that, because these scopes can be simultaneously accessed by
multiple users and/or processes, there exists the possibility that the data
can become corrupted. Locking access to these variables prevents this
corruption.
For example: Say there is a variable in the Application (or session or
server) scope called Application.SomeVar. If user A begins to write data to
this variable at the same time that user B is reading the data then the data
could become corrupted.
Make sense?
Regards,
Seth Petry-Johnson
Argo Enterprise and Associates
------------------------------------------------------------------------------
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.
