I will leave it to others to point to the entire chapters in
documentation that discusses these issues as well as
white papers and discussion lists and give the 10 second
Normal HTTP request-response are stateless. No data is
one request to the next under normal conditions. To allow
persist ColdFusion (and most other web languages in one way
create persistent scopes. ColdFusion offers several levels
of scopes to persist data; server, application, session,
cookie to name some and request sort of in a way.
Each of these scopes of different purposes and
are specific to a user (session and client) some to an
(application) and some to an entire server (server). Some are
memory on the server (session, application and server) some
client either in memory or a file (cookie).
Locking is a concept to protect data from race conditions.
applications can be accessed by multiple people from multiple
at the same time, sometimes applications can attempt to
change the data
in a common variable to different values at the same time.
this can cause serious consequences to an application, i.e a
condition. When this is the case, locking can be employed to
the value of a variable to be changed one at a time, but this
serious performance consequences so adjudication needs to be
when and how much should be locked at any given point. In
(pre-CF5) there where bugs and problems with the global
server, application and session so universal locking with was
workaround to avoid these problems.
Ok, that took way more then 10 seconds. You can see this is a
topic. If you are a beginner who wishes to learn more, I
recomened reading the documentation and other published
if you have specific questions about certain aspects of what
you read we
can help clarify the concepts.
Usually such broad and global questions do not receive much
responses from a list such as this.