No, it isn't, because I presume you'll have an EXCLUSIVE lock in the include file, putting an EXCLUSIVE lock inside a READONLY lock. Bad, bad, bad.
We've found using Application variables generally isn't necessary. We include a file in Application.cfm that sets all the global variables we need in the Request scope. > -----Original Message----- > From: Mike Alberts [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 13, 2003 2:02 PM > To: CF-Talk > Subject: Another Locking Question > > > Ok, I thought I had the locking thing squared away, but after > reading this thread, I realize that I do not. I was not aware > of the potential problems of using an exclusive lock in the > Application.cfm file. > > So ... is this (psuedo) code a reasonable solution? > > Open readonly lock > > If NOT IsDefined(SomeApplicationVariable) > > cfinclude template = "file to initialize app variables" > > close cfif > > close readonly lock > > Mike > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
