About locking Application variables

Question

Regarding Application variables, the CF documantation states:
"This issue is a problem even for write-once read-many variables
..... "
I have an application where Application variables
('Application.dataSource' and 'Application.(instanceObject of a
cfc)' are created in Application.cfc and only read, never modified
or otherwise written to in any of the templates.
Could there possible be race conditions or some other reason
to need locking in this situation? Is there really a need to test
for the existence of these variables with the templates all being
under Application.cfc?
Someone, please throw some light on this subject.
Carlos

Kevin_Schmidt · Answer

I wouldn't worry about locking them when you create them. If you are only reading from them, then create them in the onApplicationStart method of application.cfc.

As far as checking for their existence, well you could argue either way. I personally wouldn't. But that's me, I'm sure there are others out there who would.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded